#requirements
3 articles
01
·Engineering Process·FREE·8 min read
Upstream Engineering from Scratch — Why Projects Are Won or Lost at Requirements
Requirements, then high-level design, then detailed design — why that order? The reason is a branching factor that multiplies at every stage, making the cost of a late fix grow exponentially. Explained from zero with an analogy, a formula, an interactive plot, and code.
02
·Engineering Process·★ MEMBER·12 min read
The Craft of Requirements — Why "We Built Exactly What They Asked For" Fails
Why shipping precisely what a stakeholder asked for produces software that works and nobody uses. Stated versus latent needs, use cases, turning "fast" and "secure" into numbers, and a set of question templates that expose ambiguity on the spot.
03
·Engineering Process·★ MEMBER·9 min read
Upstream Work in the AI Era — When Code Gets Cheap, What Gets Valuable?
When implementation gets cheap, which parts of the cost remain, and what becomes expensive by comparison? We put the relationship between deciding and reworking into an equation, then design specs for AI as lossy compression of intent — starting from zero assumed knowledge.