Velocity Is Up. Ask Why Your Team Is So Quiet.
The engineer has been at the company three years. Senior. Knows the system well. Knew it, anyway. The codebase has been moving fast since the AI tools arrived. New services, new patterns, new surfa...

Source: DEV Community
The engineer has been at the company three years. Senior. Knows the system well. Knew it, anyway. The codebase has been moving fast since the AI tools arrived. New services, new patterns, new surface area every sprint. The features are shipping. The metrics look clean. Someone in a leadership meeting said the word "10x" and nobody pushed back because the PRs are right there on the board, merged and closed. I was in those rooms. I said the right things about momentum. Then something breaks. And the engineer sits down to debug it. Six months ago, they would have known exactly where to look. Not because they're exceptional. Because they wrote the relevant code. They had the context in their hands. The muscle memory was there. You build that over years of writing, breaking, fixing, and writing again inside the same system. It lives in you before you think to use it. Now the code was generated. The patterns aren't theirs. The structure is mostly right. And the engineer is staring at somethi