Vibe Coder · Unit 6: Thinking in Products · Lesson 9 of 9

Technical trade-offs

Engineers: make the early technical choices on purpose, write down why, and keep them easy to change.

Read the short notes and pictures.Do everything inside a blue frame.

Choosing on purpose

This course uses Next.js, Supabase and Vercel because they are widely used, well documented and well understood by coding agents. As an engineer you should still know what you are trading, and record the decisions so they can be revisited.

A 3D scene of coloured blocks and cards. Decide: where data lives, how people sign in, where code runs.
Data, sign-in and hosting.

The decisions that matter early

Data model

The few tables your one job needs. Hard to change later, so think now.

Auth

Use a provider. Do not write your own.

Hosting

Start with the simplest thing that deploys from Git.

AI provider

Keep the model call behind one function so you can switch.

A 3D scene of coloured blocks and cards. A decision record: Choice: Supabase for auth and data, Why: one service, good free plan, Revisit if: we need our own backend.
The choice, the reason, and what would change it.
ActivityBuild stepYour product spec

Record your technical decisions

Write a three-line decision record for data, auth, hosting and your AI provider. Ask Claude to challenge each one, and add the records to the spec.

Done when

These become the first section of your CLAUDE.md file in Unit 8.

Keep these

  • Make early technical choices deliberately.
  • Record the choice, the reason and when to revisit.
  • Prefer common, well-documented tools.