Claude Code is Changing the Way I Make Stuff

Hiiii, its been a minute. I wanted to write more this year but we see how that’s gone. Well anyway I wanted to talk about Claude Code so here I go.

Coding/programming was honestly not that difficult to teach myself, when I first learned the basics about print statements, if/then logic, and loops it clicked in my brain pretty easily. Not trying to flex I swear, what I’m about to say next proves that - intermediate to advanced coding is HARD STUFF. Usually this is when I’d find myself endlessly watching videos to understand concepts, endlessly scrolling Stack Overflow - all to just barely understand the concepts. What this would result in is a lot of ideas for code that started but never got finished just because the time it took to fully understand it or make it exactly how I wanted just wasn’t worth it.

Then I tried Claude Code - it hit different.

I started using it casually — tossing in a few questions here and there, asking it to explain a tricky React component or help me debug a Supabase schema. But pretty quickly, I realized something: this wasn’t a code generator; it was a thinking partner.

Claude isn’t just filling in lines of syntax. It’s reasoning with me. It gets context, style, and intent. It remembers what I’m building, suggests improvements that actually make sense, and somehow never loses its cool when I just throw millions of ideas and just brain dump in huge, usually run-on sentences (which I do a lot).

I think for me the biggest benefit is dealing with frontend development, having the ability to just have a frontend skeleton built out in a minute or two is WILD. I’ve also been using Bolt and Loveable for this and just try to imagine what it was like to be a frontend developer just a few years ago - SO MUCH copying and pasting!!

When I started building my first real software product, Claude Code became a daily collaborator. I’d describe a problem in plain English — “Hey, I need to restructure my API call flow so the editor page loads faster” — and Claude would break it down step by step. Not just what to do, but why each piece mattered.

The craziest part? I’ve been making stuff and adding new features faster than ever, and my codebase feels cleaner. I’m thinking more about architecture and less about syntax. In a way Claude makes me feel more like a “real” developer than any other tool I’ve used. I try not to rely on it too much, and will occasionally humble myself when I have an idea, tell Claude to “be honest with me and don’t tell me my idea is good just because i said it”, and then it tells my that my idea is actually not good - those moments are great learning lessons. But in general, being able to spend more time thinking and less time copying and pasting has been a very welcome change.

And honestly, that’s what’s exciting about this next wave of AI tools — they’re not replacing developers; they’re amplifying us. Claude Code has become part of my daily rhythm: a conversation, a brainstorming session, a sanity check, and sometimes just a hype buddy when a build finally works.

If this is what AI-assisted development feels like now, I can’t wait to see what it looks like six months from now!

I know this isn’t on Medium like usual but I hope you like it -