A startup is a young organisation searching for a product people need and a way to deliver it repeatedly. For engineers the work is unusual: few people, unclear requirements and constant change. The core skill is learning quickly what matters, building just enough of it and being honest about what the evidence says.
Key concepts
- Problem-solution fit: confirm a real problem exists, with real people, before building much.
- Minimum viable product: the smallest thing that tests the riskiest assumption.
- Iteration: short cycles of build, measure and learn, with the freedom to change course.
- Technical choices: simple, familiar tools often beat clever ones when time is short.
- Technical debt: taken knowingly and repaid deliberately, not by accident.
Vocabulary
- Pivot: a change of direction based on what was learned.
- Product-market fit: the point where a product clearly meets a real need.
- Prototype: a rough model made to answer a question, then often discarded.
- Founder: someone who starts the venture and carries its early decisions.
What to study, in order
- Interview several potential users about their problem, without describing your solution.
- Build a prototype in a weekend that tests one assumption, and write down the result.
- Learn to deploy simply: one server or managed platform, automated, with logs.
- Practise writing requirements as small testable user stories.
- Study case studies of failed ventures to see which assumptions went untested.