Principles before tools
If a chapter only makes sense with today's model name, it is tooling — not a principle that survives tool churn.
Spin-out from AI-Native Product Building.
Claim
AI-native product building is not "how to use Cursor." It is how to build any product when generation is cheap, judgment is scarce, and tools rename themselves every quarter.
The durable stack:
Principles (years)
↓
Decisions (quarters)
↓
Workflows (months)
↓
Tooling (weeks)
The five rules (compressed)
- Principles before tools
- Humans own outcomes
- Prototype to learn, code to own
- Artifacts over vibes
- Version in public
Pressure-test
- Could you teach this chapter with vendor names redacted and it still holds?
- What decision are you paid to make that no model should make for you?
Related
- Handbook: Mindset
- Making Software — essay rhythm we borrow, not tool tutorials