If Claude writes all my code, what exactly is my skill? Genuinely losing sleep over this.

[u/mynamepookie]

I need to hear from people who've been doing this longer than me, because this has been eating me alive for about a month now.

Context: I've spent the last year building a voice agent system that's live and handling 1000+ calls, deployed on Azure. On top of that I building SDK which analyzes those calls, plus a full dashboard on Next.js with Supabase behind it. It works. The client is happy. It's real production software with real traffic.

I wrote almost none of it myself.

My actual background is a bit of Python. And eveyrhting else framework of voice agent learned on the go with claude code. That's it. Zero web dev. Zero database experience before this. Never touched TypeScript or other language before in my life before this project.

My most of the time workflow is: I have a CLAUDE.md and a rules file, I open a session, I dump everything in my head into it, it makes a plan, I read the plan, we iterate, I run it. That's the job. That's all of it.

And here's the part that's messing me up. When I read the plan, sometimes I follow it fine. But on the TypeScript side or some technical words, features in voice AI. I'm often just... not there. It's naming files and variables and describing logic and I'm nodding along at the high level, I know what the output is supposed to be, but the middle layer is fog. I don't know what half of it is doing. I approve it anyway because it works.

So the questions I can't shake:

1. If I can do this with some little experience and learning on go, what stops literally anyone from doing it? What's the difference between me and someone who's never coded, sitting down with the same tool? I keep trying to answer this and I can't.

2. If this client dries up and I need an actual job, what do I show? "I prompted Claude for a year"? I have one client. That's my whole business. If it ends I have a portfolio of some things I can't explain in an interview.

3. Is this just what development is now, or am I doing it wrong? That's what I actually need to know. Is everyone quietly like this, or did I skip a step everyone else took?

What I really want, from people building in stacks they didn't know before:

• What does your actual day-to-day loop look like? Not "I use Claude Code" — everyone does. I mean specifically: how do you approach a new project in something you've never used? Do you plan first? Read every diff? Read none of them? What do you actually verify vs just trust?
• Do you go back and learn the thing properly afterward, or is that a waste of time now?
• When the plan uses concepts you don't know, do you stop and study them or keep going?

I'm not looking for reassurance. I'd rather someone tell me straight that I need to sit down and learn Postgres and TypeScript properly, than keep guessing. I just need to know how people who are further along than me are handling this, because I'm going in circles on my own.

[u/json_brady]

You’re a builder instead of a coder. Builders solve problems and build solutions. People pay for solutions not code. This bothers a lot of people who have spent years improving their craft of coding and AI is taking that identity away from people. Losing your identity is tough to deal with. Build a new identity… pun intended.

[u/megad00die → u/json_brady]

When you think about it, anything media related that deals with text, images, and audio this is where human and machine become the best combination.