「ノーと言うエンジニア」の役割はZIRP時代の产物だった
ノーを言うエンジニアの逆風品質と保守性を重視し、複雑な機能開発に反対する「ノーと言うエンジニア」は、かつてゼロ金利政策（ZIRP）下の急速なテック企業成長期において貴重な存在でした。
しかし、ZIRPの終焉と企業が利益追求にシフトしたことで、開発環境は劇的に変化しました。
現在、AIを活用した迅速な機能追求が優先される傾向が強まるにつれて、彼らは組織内で軋轢を生んでいます。
皮肉なことに、本来は彼らが防衛すべきAI生成コードが「十分使える」レベルに達し、彼らの専門的役割はアイデンティティの危機に直面しています。
原文の冒頭を表示（英語・3段落のみ）
The engineer who says no all the time is a real archetype among senior and staff engineers. Their role is to slow things down, to block the development of features that add complexity, and to ensure that as little code gets written as possible (since code is a liability).
We can think of this as the just-say-no engineer1, as opposed to the just-say-yes engineer. The just-say-yes engineer is obsessed with moving fast, approves code changes by default, values MTTR over MTBF, and tends to ship a lot of code. The just-say-no engineer is obsessed with quality, is happy to move slowly, and blocks code changes by default. Most engineers are somewhere in the middle of the spectrum. By “just-say-no engineer”, I’m talking about the group of engineers who most strongly identify with that archetype.
The just-say-no engineer is having a hard time in the era of AI. It used to be that they only had to say no to more junior engineers’ handwritten PRs, but now they have to say no to a barrage of AI-generated code, some of it generated by managers and VPs who are politically difficult to say no to. For the first time in their careers, they’re under a lot of pressure to lower their standards and start saying yes. However, this isn’t because of AI. It’s because of the end of ZIRP.
※ 著作権に配慮し、引用は冒頭3段落までです。続きは元記事をご覧ください。