The just-say-no engineer archetype was a product of the ZIRP era

Summary

This article examines the "just-say-no engineer" archetype — a senior/staff engineer who deliberately slows down development, blocks feature complexity, and minimizes code output because code is viewed as a liability. It contrasts this with the "just-say-yes engineer" who prioritizes speed and shipping. The article argues that the just-say-no engineer was a product of the ZIRP (Zero Interest Rate Policy) era, when tech companies had abundant capital and could afford to prioritize quality and long-term thinking over speed. With the end of ZIRP, the incentives have shifted, making the just-say-no approach less viable in today's faster-paced, resource-constrained environment.