Story
The just-say-no engineer was a ZIRP phenomenon
1 report
1 website
1 discussion
Latest report
Overview
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.
Summary from seangoedecke.com.
Reports
One report so far. Additional coverage will appear here when it is linked to this story.
seangoedecke.com
The just-say-no engineer was a ZIRP phenomenon
Read report →
Community reactions
Each reaction summarizes sampled comments from the linked discussion.
Hacker News · seangoedecke.com
Hacker News discussion ↗
Historical count: 5 · 5 saved in sample · Historical sample
Analysis ready
Read this discussion’s reaction
Based on 5 sampled comments from this thread. Analyzed 2026-05-27.
- Praise: 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.
- Praise: The emergence of AI-generated code is reshaping the dynamics of engineering teams, prompting necessary discussions about code quality and managerial involvement.
- Concern: The influx of AI-generated code from upper management complicates the review process, potentially leading to poor quality and increased technical debt.
- Concern: The perception that engineers are merely gatekeepers to deny proposals reflects a cynical view of productivity and innovation within tech companies.