The Decision
I just downgraded from Claude Max to Claude Pro. On paper that's a strange thing to write a blog post about it's a billing change, not an engineering decision. But it was the most deliberate decision I've made about how I work in months, and I think it's worth talking about honestly.
I wasn't downgrading because Max was too expensive or because I wasn't getting value from it. I was downgrading because I wasn't getting value from myself anymore, and I'd convinced myself that was fine.
How It Actually Happened
When you're on Max, there's effectively no friction between having a thought and outsourcing it. Small bug? Ask Claude. Not sure how to phrase a function name? Ask Claude. A design decision I could've reasoned through in ninety seconds? Ask Claude, get an answer in three, move on.
None of those are bad decisions individually. That's exactly what makes it dangerous individually, every single one is defensible. The tool is fast, it's usually right, and there's no visible cost to reaching for it. So I reached for it constantly not because each task needed it, but because the door was always open and closing it took more effort than walking through it.
I told myself I was being disciplined about it. I'd say "I'll only use it for the hard stuff" and then define almost everything as hard stuff, because on some level, if AI can answer it, why wouldn't I let it? I tried to self-regulate multiple times. It didn't stick. The plan was unlimited, so my usage found a way to become unlimited too.
What I Actually Noticed
The thing that finally got my attention wasn't a single dramatic moment. It was smaller and slower than that a kind of muscle atrophy I only noticed in hindsight.
- ▸I'd stare at a bug for ten seconds before typing it into Claude, instead of thirty seconds actually thinking about it
- ▸My first instinct for almost anything unfamiliar became "ask" instead of "read the docs" or "trace it myself"
- ▸I noticed I was worse at holding a whole system in my head, because I'd been letting the model hold the context for me
- ▸Debugging sessions that used to sharpen my intuition started to just... resolve, without me learning much from them
None of this made me a worse engineer overnight. It's more that the parts of the job that used to build understanding the friction, the dead ends, the "wait, why does this happen" moments were getting sanded down before I even felt them. And those moments are where the actual learning lives.
The tool wasn't the problem. I was using it exactly as well as it was designed to be used. The problem was that nothing in my workflow was pushing back on me, so I never had to ask whether I should be doing this myself.
Why a Downgrade, Not Just Willpower
I tried the willpower route first "use it less," "only for real blockers," "think first, ask second." It didn't work, and I don't think that's a personal failing so much as a predictable outcome. When the cost of an action is invisible, intentions don't hold up against habit. I wasn't choosing to over-rely on it in any given moment I was just doing what was easiest, over and over, until it became the default.
So instead of trying to out-discipline an unlimited plan, I removed the unlimited part. Claude Pro has a real usage limit. When I hit it, I have to stop, or wait, or actually solve the problem in front of me without it. That's the whole point. I'm not hoping the limit never bites I'm hoping it bites often enough that I have to relearn what it feels like to sit with a hard problem before reaching for help.
It's the same logic as leaving your phone in another room to focus, or unsubscribing from a feed instead of promising yourself you'll scroll less. Environment design beats willpower almost every time. I just applied it to a subscription tier.
This Isn't an Anti-AI Take
I want to be clear about what I'm not saying. I'm not saying Claude Code or Claude Max are bad, or that AI tools make you a worse engineer, or that anyone using Max is doing something wrong. I still think these are some of the best engineering tools that have existed in my career, and I'll keep using Claude daily including for this exact blog post.
What I'm saying is narrower access without limits changes behavior, and it's worth being honest about how it changed mine. A tool being powerful and available at every moment doesn't mean every moment is improved by using it. Some of the value in this job the pattern recognition, the intuition for where bugs hide, the ability to reason about a system you can't fully see comes specifically from the reps you get when there's no shortcut available.
Take those reps away entirely and you don't just get faster you get dependent, quietly, without ever deciding to be.
What I'm Actually Hoping For
- ▸Hit the Pro limit regularly enough that stopping and thinking becomes a normal part of my day again, not an emergency
- ▸Rebuild the habit of trying something myself first, and only reaching for AI once I actually know what I'm asking for
- ▸Get back some of the slower, deeper thinking that made debugging and design feel like skill-building instead of prompt-writing
- ▸Use the model more deliberately when I do use it fewer, better-formed questions instead of a constant low-effort stream
I don't know yet if this sticks. Maybe in three months I'll be back on Max because the limit became its own kind of friction that just slowed me down without teaching me anything. That's a real possibility and I'm happy to admit it if it happens. But right now, today, hitting a wall sounds like exactly what I need.
Wrapping Up
If you're a developer reading this and something about it feels familiar the reflex to ask before you think, the sense that your own problem-solving has gotten a little quieter it might be worth asking whether your tools are unlimited by accident. Not because the tools are wrong, but because unlimited access removes a kind of resistance your brain actually needs.
Sometimes the most useful upgrade is a downgrade. Mine just happened to come with a smaller invoice too.