There's a quiet trade-off happening in workplaces like the one described, and it deserves more attention than it gets. The poster didn't lose their technical edge because they stopped caring. They lost it because they optimized for speed and delegation, and the cost was invisible until it wasn't. That's the real risk of letting AI do your thinking: not that the work won't get done, but that the ability to do it yourself quietly erodes, and you don't notice until you're staring at a problem you know you used to solve without breaking a sweat.
This isn't a warning against using AI. It's a warning against using it as a substitute for the kind of deliberate effort that keeps skills sharp. The poster's experience is telling because it wasn't laziness or neglect. They were moving fast, managing stakeholders, scoping projects, and shipping. That's what gets rewarded. But the technical reps, the reps that build and preserve fluency, were outsourced, and within a year, the mental models started to fade. That's not a moral failing. It's how brains work. Skills don't stay sharp because you once had them. They stay sharp because you keep using them in ways that require some resistance.
What makes this story stick is the "brain fog" detail. It's not that the knowledge is gone. It's that the retrieval pathways have grown over. The poster can look at a problem and know they've solved it before, but the route to the answer feels unfamiliar. That's the difference between learning and delegating. Delegation is efficient in the moment. It gets the task done. But it doesn't build the neural architecture that makes you self-sufficient. And when you need that self-sufficiency, when the AI isn't there, or the problem is novel, or you're back in an environment without the crutch, you're starting from a weaker position than you think.
The practical takeaway isn't to reject AI or to romanticize slow, painful work. It's to be intentional about what you hand off and what you keep. If you let AI draft your code, spend time reviewing it critically. If you let it outline your analysis, force yourself to explain the reasoning back in your own words. Use it to accelerate, not to abdicate. The poster's advice to avoid getting "GPT brained" is more than a warning about dependency. It's a reminder that your edge, long-term, comes from the reps you refuse to skip. The work you choose not to delegate is the work that keeps you sharp. That's not nostalgia. That's just the price of staying capable.