The just-say-no engineer was a ZIRP phenomenon
seangoedecke.com
May 27, 2026
10 min read
🔥🔥🔥🔥🔥
55/100
Summary
The just-say-no engineer archetype among senior and staff engineers focuses on minimizing complexity and reducing code development, viewing code as a potential liability. This contrasts with the just-say-yes engineer, who prioritizes rapid progress and readily approves code changes.
Key Takeaways
- The just-say-no engineer archetype is characterized by a focus on quality and a tendency to block code changes, contrasting with the just-say-yes engineer who prioritizes speed and rapid deployment.
- The era of zero interest rate policy (ZIRP) from 2008 to 2022 allowed tech companies to hire aggressively, leading to a bloated engineering workforce that required oversight from just-say-no engineers.
- The end of ZIRP resulted in widespread layoffs in the tech industry, as companies shifted focus from growth to profitability and could no longer sustain large engineering teams.
- The rise of AI technologies like ChatGPT has been used by tech companies to justify layoffs, framing them as a means to achieve greater efficiency with fewer engineers.
Community Sentiment
Positives
- The distinction between 'just-say-yes' and 'just-say-no' engineers highlights the critical balance between speed and quality in software development, which is vital for long-term success.
- The emergence of AI-generated code is reshaping the dynamics of engineering teams, prompting necessary discussions about code quality and managerial involvement.
Concerns
- The influx of AI-generated code from upper management complicates the review process, potentially leading to poor quality and increased technical debt.
- The perception that engineers are merely gatekeepers to deny proposals reflects a cynical view of productivity and innovation within tech companies.
