Senior devs frame problems as complexity management; the rest of the business frames them as uncertainty reduction, causing a persistent communication mismatch.
Key Takeaways
The business’s first loop (sales, marketing, product) optimizes for speed to reduce uncertainty; the second loop (serving customers) optimizes for stability via complexity management.
Senior devs’ core skill is resourcefulness: reusing existing software instead of building new, captured in the phrase “Can we try something quicker?”
AI accelerates the speed loop but worsens the stability loop by degrading understandability, debuggability, and teachability while taking no responsibility.
Proposed mitigation: decouple into a “Speed” system (AI-assisted, experimental) and a “Scale” system (senior-reviewed, stable), with features graduating from one to the other.
Senior developers should reframe their role from writers to editors, reviewing and hardening what the speed layer produces.
Hacker News Comment Review
Commenters pushed back on the binary “avoider vs. experimenter” framing, noting that domain context matters – firmware for a CT scanner demands a different default posture than a web MVP.
A recurring thread argued the real blocker is incentives, not language: people whose jobs depend on shipping features won’t respond to reframing alone, regardless of how well a senior dev communicates.
The Speed/Scale decoupling idea was met with skepticism grounded in experience: proofs of concept reliably become production systems, and promised rewrites almost never happen, making the two-system model aspirational rather than operational.
Notable Comments
@hamstergene: Senior expertise lives in an internal world model that is hard to transfer in words; the gap is epistemological, not just rhetorical.
@nitwit005: “What ‘the company’ wants doesn’t matter, it’s what the people making particular decisions want” – individual incentives override organizational framing.
@luodaint: The harder communication gap is product sense – knowing which user feedback signals a real trend – not whiteboarding distributed systems.
