This article shares why a web engineer holding a Claude Code Max 20x plan has mostly stopped using AI for coding at work. It's not about abandoning AI — it's about narrowing down where I let AI take over.
Why I stopped having AI write my code
My growth pace slowed down
Looking back honestly, I was acquiring knowledge faster before I delegated most coding to AI. Once I drastically cut down on writing code by hand, I quietly gave up a side benefit: the investment in growth that came along for the ride with the act of writing.
In learning theory terms: output (writing) drives retention more strongly than input (reading), as evidenced by the addon gems for myself, which enable VS Code go-to-definition for Rails DSL methods (scope, delegate, etc.) and CodeLens display of model associations. The vibe is "as long as it runs" — and I haven't written a single line of that code by hand.
These use cases tend to fill up my Claude Code usage anyway, so I'm keeping the Max 20x plan.
Closing thoughts
Things feel settled at the moment, but technology moves so fast that I might be saying the opposite tomorrow. Personally I expect that "coding" itself will eventually get fully abstracted away by AI — and this article, which kind of swims against that current, may quietly disappear one day.
Even so, I'll keep enjoying day-to-day engineering through this turbulent era.
SOCIAL SHARE CARD GENERATOR