Choose a tech stack by testing constraints
A decision framework for choosing technologies based on product constraints, team familiarity, operating burden, and reversible learning.
A practical wiki for people building independent products. Clear steps, real trade-offs, and sources you can check.
Try “first users”, “AI security”, or “launch checklist” Press / to search
Turn a hunch into a clear problem and a testable next step.
02 / LEARN FROM PEOPLEFind relevant people, run focused conversations, and learn before you scale.
03 / GET IT OUTCheck the product, the path to users, and the parts that can fail.
Twenty connected areas, one searchable library.
Choose a problem worth your attention and find a starting point.
Learn from potential customers before overbuilding.
Shape a useful product and keep scope intentional.
Make implementation decisions you can maintain.
Work effectively with coding assistants and agents.
Choose tools around constraints, not hype.
Make software accessible, secure, clear, and dependable.
Release safely and learn from real use.
Find and reach the people who need your product.
Have useful conversations and make clear offers.
Price and package around value and sustainability.
Help users reach value and keep getting it.
Keep a small product and team healthy over time.
Understand the operating work around a product.
Repeatable workflows for common builder tasks.
Practical prompts for high-leverage reviews.
Context-rich examples, with limits made explicit.
Evaluate tool categories with clear criteria.
Starting documents you can adapt to your context.
Definitions and durable concepts in one place.
Short, evidence-aware guides for the decisions that shape a small product.
A decision framework for choosing technologies based on product constraints, team familiarity, operating burden, and reversible learning.
A realistic early distribution loop: narrow the audience, learn where they gather, and earn relevant conversations before automating outreach.
A risk-focused checklist for reviewing common application security boundaries, with special attention to generated code and agent tool access.
A practical way to move from an interesting idea to a testable question without committing to a large build.