The just-say-no engineer was a ZIRP phenomenon
2 days ago
- #software engineering
- #AI impact
- #ZIRP
- The 'just-say-no engineer' archetype focuses on blocking features, reducing complexity, and minimizing code as a liability, prioritizing quality over speed.
- During the ZIRP era (2008-2022), these engineers were valuable for controlling rapid, often unproductive engineering growth fueled by cheap capital and hiring surges.
- Post-ZIRP, with rising interest rates and layoffs, tech companies shifted focus to profitability, undermining the role of just-say-no engineers, who now face pressure to approve more changes.
- AI tools, while often blamed for industry shifts, exacerbate the decline of just-say-no engineers by enabling more code generation, but the core change stems from economic rather than technological factors.
- Just-say-no engineers may survive in 'pure engineering' domains like core infrastructure, where high quality and slower cycles are acceptable, but their influence is more limited compared to the ZIRP period.