Executive TL;DR
- The just-say-no engineer phenomenon emerged during the ZIRP era.
- Code quality puritans played a crucial role in protecting codebases.
- The end of ZIRP may lead to a shift in engineering priorities.
The Buzz Score
The Internet’s Verdict: 60% Hyped, 40% Skeptical
Forum Voices
Some argue that the just-say-no engineer is a necessary part of the development process.
Code quality puritans are annoying but if they do their job right they actually speed-up the development process because they don’t let technical debt accumulate.
Others see this role as a product of the ZIRP era.
Having half of the company’s engineers enmeshed in an endless loop of proposing changes and being told no was totally fine – they didn’t need to be productive anyway, and this way they weren’t impacting business-critical systems.
Expert Analysis
With the end of ZIRP, companies may need to reevaluate their priorities and investment strategies.
This could lead to a greater emphasis on efficient development and a reduced need for the just-say-no engineer.
Focus Keyword: Just Say No
