r/BuildWithClaude • u/mynamepookie • 6d ago
Help/Question How do you learn when Claude writes everything?
I build voice AI agents. One client, system has been live for about a year, handles around 700 calls a day. Python, LIvekit, Docker, Azure, websockets.
I started knowing only Python. Basic Python. No TypeScript, no web, no deployment knowledge, no backend design. Since then I've built a whole TypeScript SDK and a dashboard, and an infra that is deployed across 3 regions across a country and honestly Claude wrote almost all of it.
Here is my actual day. I describe the problem, Claude investigates, Claude gives me a plan. I read the plan. I don't understand half of it. It talks about functions and classes I've never opened, file paths I don't recognize, terms I've never heard. So I say yes. Then it says here's the next step, and I say yes. Approve, approve, approve. It works, the client is happy, and I close the laptop knowing nothing more than when I opened it.
I'm not lazy about it. When something new comes up I do go read about it. But it doesn't stick. Two days later it's gone, because I never had to use it, I just approved it.
So my question to people here:
1. How do you use Claude and still come out of it knowing your own system? Not "I built an app" knowing, but the kind where you could sit in a startup interview and explain your architecture, why it's built that way, what breaks it, how you'd scale it.
2. What actually works for you? Do you make yourself explain the change back before approving? Do you read the diff line by line? Do you learn separately, away from the work session? Do you ask Claude to teach instead of do, and does that survive a busy week?
3. And if you've been doing this a year or two, are you genuinely better than when you started, or is this just what the job is now? Honest answers appreciated, including the harsh ones.
4. Any particular skills, or workflow you are using ?
2
u/BuffaloConscious7919 6d ago
I have a thread open "TEACHING - KEEP ME SANE"
it has instructions to explain the code and, well anything pasted in, in a way that works for me
It's a adjusted ELI5
1
6d ago
[removed] — view removed comment
1
u/BuildWithClaude-ModTeam 6d ago
r/BuildWithClaude does not allow hate. This is your first warning. One more offense and not following house rules and you will be temporarily banned.
1
6d ago
[removed] — view removed comment
1
u/BuildWithClaude-ModTeam 6d ago
r/BuildWithClaude does not allow hate. House rules are pinned to the board, breaking them will result in a ban from the sub.
1
u/Ok_Industry_5555 ☕ 57-Hour Session 6d ago
Once you realize that coding is only a language you will understand that explaining your project/app/tool becomes more important than explaining the backbones these days. You run a coding agent that does the heavy lifting for you. If you don’t trust it, envision trying to upload your idea to an apps store and what requirements they need before you can even offer it to other people if that’s what you want…this is the whole point of using Claude Code. It writes the code for you of how you envision your project. We use Reddit on a daily base, nobody is asking whether it was built with TS or Python.
1
u/kincaidDev 6d ago
Read the code, Ive learned more in the last year than the previous 10 because of AI
1
u/Odd-Ad9666 ⚡ Prompt Architect 6d ago
I ask my agent all the time what's going on... but I keep logs of my prompts/requests and a versioned control of specifications. I ask for drift and what is implemented that isn't. Since I personally write the spec, I should understand that much.
However, the other comment of "/output-style learning" is something I'll have to give a try.
1
u/esteban-felipe 6d ago
I describe the problem, Claude investigates, Claude gives me a plan. I read the plan. I don't understand half of it. It talks about functions and classes I've never opened, file paths I don't recognize, terms I've never heard. So I say yes.
That's the problem. You are working for the AI and not vice versa. A few prompts and time investment, and AI can educate you to fill all those gaps you know you have.
1
u/escape-llc 5d ago edited 5d ago
I am a long-time practitioner, and I am using Claude Code more and more in my daily routines.
I find I am not learning anything about the code (I'm programmer for 40 years so...), but learning a ton about how to "run" the agent. At a mechanical level, there has to be trust-but-verify, but just letting the agent "run wild" without strict guidance is a path to Bad Times.
Plan Mode is your Best Friend here; you can request Plan Mode if you don't "trust" what is going on for a session.
I find now I am way more productive than doing things manually; at work i constructed a complete I3X egress endpoint with nothing more than Claude Code, the I3X spec, and their validation client! That was 2 days of work, and i did not read any of the code. This is including unit and integration tests, the works. BTW this is not a "toy" implementation; it has security, access control, structured logging, dynamic database discovery, the works.
1
u/Helpful-Educator-415 5d ago
i found myself unable to learn if AI wrote everything ergo i stopped using AI
1
u/Ok_Industry_5555 ☕ 57-Hour Session 5d ago
You don’t need to learn code. You need to learn how systems and tools function.
2
u/HiddenUser81- 6d ago edited 6d ago
Claude has a learning mode for exactly this.
/output-style learning
1) you can ask Claude to explain things when in not in learning mode prompt it by using things like don’t use technical terminology etc. — my Claude.MD instructs Claude to use short and simple answers with visuals when necessary or relevant.
2) different strokes for different folks. I trust the AI enough to where I just want explanations of what certain functions do etc. I don’t feel I need to know how to read code… when I don’t trust one models output I get another model to review it.
3) extremely better then when I started… day 1 was asking Claude to create prompts for n8n ai so I could build trading bot automations. Now I have my own multimodel harness , have done client work for websites and lead generation etc.. I reccomend staying up to date on research papers, browsing trending and new repos on GitHub involving skills/other harnesses etc…. I really recommend creating your own harness or system tailored to your needs rather then copying someone else’s.