
We're losing our ability to understand the code we wrote. We're starting to trust AI more and more with the outputs. But how do you trust that AI is always right if you don't do the proper due diligence or research yourself? After interviewing many engineers who use AI on a daily basis - one pattern I've observed is that their mental model of the codebase has diminished. The most perplexing part: they are completely self-aware of this shift, and understand that it's a bad thing. Why is this important? 6 months down the line, when the CTO asks you "how does this work" and "why did you make this technical decision", what will you answer? What happens when you or someone on your team is on-call - how long will it take to resolve an incident? Will your decision stand the test of time or will your team be left with the refactor? Engineers should be understanding the impact of the changes they make. One-shotting a PR is unsustainable - even if you are reviewing the final PR. You haven't spent enough time understanding the system and the change to be confident about the end result. They say it takes 2-3 years to understand the consequences of your software design decisions. Was saving a few minutes worth it?
























