Reference · 10 sources
Resources
Curated links captured from reading and practice — not dumps, but sources that shaped decisions in the handbook. Open a chapter for workflow and artifacts; come here when you want the wider context.
How this list works
Draft notes and synthesis stay private. Only public URLs ship here, mapped to the chapters they inform. When a principle is sharp enough to stand alone, it may also appear onfootnotes as a spin-out essay.
Books
Past behavior over future promises — the discovery and validation classic.
Chapters:Finding problems worth building, Discovery and research with AI, Validation before code, Analytics and feedback loops
Courses
Builder PM craft — product judgment for people who ship vertical slices.
Chapters:Mindset — product engineer vs software engineer, Finding problems worth building, UX taste and design judgment, Owning the codebase, Iteration, Teams and governance
Essays
Essay + diagram rhythm — timeless craft over changelog-driven docs.
Chapters:Principles, UX taste and design judgment, Architecture decisions, Testing and maintainability
Building imperative — institutions fail when they stop making things.
Chapters:Principles
Articles
Cross-domain builders outship specialist teams when AI commoditizes code.
Chapters:Mindset — product engineer vs software engineer, Owning the codebase, Teams and governance
Disposition, strategy, and project leadership for people who own cross-cutting work.
Chapters:Mindset — product engineer vs software engineer, Finding problems worth building, Iteration
AI should extend human judgment and local knowledge — not replace participation.
Chapters:Principles, AI pair programming, Agentic development
Practitioner view on AI-native vs enhanced vs bolted-on — stack, economics, teams, compliance.
Chapters:Principles, Architecture decisions, Deployment, Analytics and feedback loops, Scaling, Teams and governance
Org design when AI changes information routing — speed as compounding advantage.
Chapters:Scaling, Teams and governance
Repos & curricula
Catalog spine for technical depth — compare structure, don't copy wholesale.
Chapters:Owning the codebase, AI pair programming, Agentic development, Architecture decisions, Deployment, Scaling
Footnotes spin-outs
Distilled principles on the public wiki — tighter essays linked from chapters.
Chapter: Principles
Chapter: Finding problems worth building
Chapter: Validation before code
Chapter: When to leave the prototype
Chapter: Architecture decisions
Chapter: Teams and governance
Pattern cards
Anonymous composite scenarios — useful shapes from practice, not named products.
- B2B scheduling tool
A small team ran a paid concierge for two weeks before app code. They left no-code only after auth and billing limits blocked the next experiment.
Chapters:Validation before code, When to leave the prototype
- Internal ops dashboard
Three teams used a vibe-built admin weekly for a month. Migration started with data model and tests; the prototype URL stayed as a learning tombstone.
Chapters:When to leave the prototype, Testing and maintainability
- Multi-file refactor with agents
Agents proposed a plan across twelve files; humans gated schema and CI changes. Shipped in small PRs with required build checks.