AI and the Demise of Software Tools

I tried to log into CodeAnywhere today. I just wanted to peek at some old code on one of my sites — figure out why I’d written something a certain way. Login kept failing. I tried again. Then I went to the homepage and saw it: after fifteen years, CodeAnywhere shut down on July 1st.

I started teaching kids to code when my daughter was in fourth grade. She’s a senior in college now. CodeAnywhere is almost that old to me — I found it back when setting up a local development environment could eat an entire class session, sometimes an entire week, just fighting conflicting documentation and mismatched versions before a single kid wrote a line of code.

CodeAnywhere solved that. Each student got a free account, one website, and they could log in from anywhere and just start working. I had a master account linked to all of theirs, so I could jump in and help no matter where they were. During COVID, that setup basically saved my program. CodePen is great, but it’s not a real dev environment. Git is solid, but it has its own learning curve. CodeAnywhere’s whole pitch was: no setup, no barrier, just code.

This spring I received a similar email from the guy behind Learn to Code with Baseball — the book I used to teach teens data science with Python. He’s closing up shop too.
Two tools I built years of curriculum around, gone in the same year. And I don’t think that’s a coincidence of business models — it’s AI. AI has quietly taken away so much of the joy of coding. Not just jobs or code review, but the struggle itself, the part where a kid stares at an error for twenty minutes and something clicks.

That struggle is the point. Schools hand-hold kids through most things now. Coding — like physics — is one of the few subjects left that genuinely rocks a kid’s world, because it doesn’t care how you feel about the answer being wrong. It just doesn’t run. There’s no partial credit, no teacher softening the blow. You either figured it out or you didn’t.

So this summer, when I taught my first “Coding with AI” class, it wasn’t open to just anyone. Every kid in that room already knew how to code — they’d already sat with an error for twenty minutes and felt it click. That was the prerequisite, not the curriculum. Only then did we bring in Claude Code, and even then the goal wasn’t “let it write your app.” It was: can you catch it when it’s wrong? Can you tell when it just confidently did something dumb? That’s a skill you can only build on top of real, hard-won understanding — never as a substitute for it.

So yes, Codeanywhere is gone, and so is the baseball book, and I felt that loss walking away from a dead login page today. I’m not going to pretend AI hasn’t taken something real from this. But it’s exactly why I think the order still matters: learn to code first, struggle through it, and only then learn to use AI — so you’re the one catching its mistakes, not the other way around.