Tried to fix a small bug WITHOUT AI, Just to see if I still could. It wasn't pretty.
My terminal coding agent had hit its weekly limit and I had a small bug sitting in my queue, the kind of thing that would normally take one prompt and thirty seconds, so I figured I'd just fix it myself while I waited.
Took me almost the full thirty minutes. Not because the bug was hard, it genuinely wasn't, but because I kept reaching for a keyboard shortcut that wasn't there and realized I'd forgotten the actual syntax for something I used to type without thinking. Had to look up documentation I would've known cold two years ago.
Got it fixed right as the coding agent's limit was reset and honestly felt a little relieved, like I'd passed some test I didn't know I was taking. But it also left me wondering how much of that muscle is still in there versus how much I've quietly outsourced without noticing, since it's not like there was ever a single moment where I decided to stop practicing it.
Has anyone else tried this on purpose, going a day without the assistant just to check? Would you actually want to know the answer, or is it better not to look too closely at how much you've forgotten?
Replies
Syntax is the cheap part. You forgot it, you looked it up in a minute, it's back. That muscle isn't really gone.
The one that actually goes quiet is different: the instinct for where to look first when something breaks. That's not knowledge you can re-fetch from docs, it's pattern from having been burned before, and the assistant only erodes it if you let it run the diagnosis too, not just the typing.
So if I ran your test I wouldn't measure syntax recall. I'd watch whether I can still form the first guess about a bug myself before I open the chat. That's the part worth not losing.
@jernej_jan_kocica That distinction is a much better test than the one I actually ran. Syntax was just the part that happened to be visible in the moment, it made a good story because it was quick to notice and quick to look up. The diagnosis instinct doesn't announce itself the same way, there's no obvious twenty minute gap where you feel it missing, you just reach for the chat a little earlier each time until you can't remember the last time you formed a real guess first.
@terranicgerald Right, there's no alarm for it. The syntax gap is loud so you notice and fix it, the diagnosis gap is silent so it just quietly widens. Which is why your test is worth running on purpose, it's the only way to hear the thing that doesn't announce itself.
I think there's a difference between forgetting knowledge and changing where you spend your cognitive effort. I probably remember less syntax than I used to, but I spend more time thinking about system design, edge cases, and whether I'm solving the right problem in the first place.
That said, I do think it's worth occasionally working without AI—not because I think we should avoid using it, but because it's a good way to identify which fundamentals are becoming rusty. Ideally, AI should replace repetitive recall, not our ability to reason through a problem when the tool isn't available.
@stephanie_t0317 That's a fair reframe, and probably the more accurate one. The syntax loss was never really the worry, it was always a stand-in for the fear that something deeper might be going quiet too. If the effort's actually shifting toward system design and problem framing rather than just evaporating, that's a trade most people would take on purpose.
I’ve noticed the same thing. AI makes you faster, but it can also weaken the habits you used to rely on without realizing it.
I do not think the answer is to stop using coding agents. It is probably better to use them intentionally. For example, I still review the code, ask why a change works, and occasionally handle smaller fixes myself so I do not lose the underlying understanding.
The skill may shift from memorizing every syntax detail to knowing how the system should work, how to verify the output, and how to recognize when the agent is wrong. But I still think doing an occasional no AI session is a useful reality check.