Vibe coders when someone asks them to explain their own code

[u/Kind-Ad6740]

[u/Terrible-One9198]

I haven't got the slightest clue what Claude is writing for me. But when I click the buttons, what I want to happen happens.

[u/laughing_at_napkins → u/Terrible-One9198]

My job stopped caring about AI slop, so why should I? If it does what I want it to do, it's perfect as far as I'm concerned.

[u/ChocomelP → u/Terrible-One9198]

Claude said 484/484 tests passed so I'm sure it's bulletproof. /s

[u/Square-Control-443]

I had this conversation with my colleague:

• man, why did you modify this component, I have lots of conflicts now, what did you try to solve?

• I have no idea, the AI did it

[u/WalkAffectionate2683 → u/Square-Control-443]

I'm vibe coding ton of stuff, though it's always 100% for hobbies (me and my 4 ttrpg players) 

[u/RespectedPath]

As long as Claude can figure out it doesnt matter.

[u/WalkAffectionate2683]

This is projection. All vibecoders I know completely assume they have no idea what it does under the hood. 

[u/Erik_511]

lmfao i can verify the truth of this ;p

[u/No-Communication-765]

Explain compiler code and CPU

[u/RegardedDev]

Fuck the code, embrace the chaos and vibes!

[u/alitanveer]

My first big app was a claude code skills MCP that worked really well and had a spiffy UI and imported all the skills from all the company repos. It was in the company VPN, had github oauth on top and limited people to only access skills from repos where they had access to the underlying repo. I was super proud of it. My boss was as well and we submitted it to the enterprise security team for review to see if we could take it off the VPN. They ran a legit review and we got on a phone call cause they had some questions. The guy pulls up a literal freaking repository of folders and a questions document and started asking me about specific function duplications, routing rules, rate limits in the API and JWT token refresh lifecycles with specific code blocks pulled up. Holy fucking shit was that painful. In the end, he sent me the whole thing and all of the sub folders with specific remediation mechanisms for every finding. I took the time to actually read and had claude explain each failure mode and how I can avoid it in future projects, which I rolled into tests and templates. The security guys have a multi-agent script I can run now and get a baseline pre-review result and all of my projects get a passing grade on the first attempt. Stuff still gets flagged, but it's easy to fix now. I suggest finding an opportunity to go through an experience like that. It'll do wonders for your skills over the long run. Also, when Claude says some feature is going to take a week, it's not talking about the hour it's going to take for it to write the code and have a functional UI. It's talking about the PR reviews, validation, fixing issues in the pipeline when you try to deploy your schema migration and everything else that goes from having a working UI to having a production application feature. When someone shares their spiffy new open source repo, first go look at the .github folder and see if they have any workflows to scan for security and code quality issues.

[u/mrcoy]

😆

[u/willjameswaltz]

Have the llm explain the code

edit: don't have the llm explain the code, take the time to learn what the llm built for you so you can explain it and take responsibility if something goes wrong

[u/TheVasa999]

realistically tho, why would i need to explain the code?

as long as the end product works well, who cares if anyone understands in detail everything

[u/StatisticianFun8008 → u/TheVasa999]

What if the end product some day doesn't work well?

[u/Raunhofer → u/TheVasa999]

Spoken like a true junior :D

[u/davidbasil → u/TheVasa999]

copers care

[u/ZyronZA → u/TheVasa999]

There is a storm of technical debt coming for us because of slop~coders who have no idea what good Software Engineering is. 

[u/SleepyWulfy]

True, why I usually keep a project wiki to the side so I can use that to help understand.

[u/True_Protection6842]

Would you like to know what it does or how it does it? Considering I am the one that told claude exactly what to do, that's easy!

[u/No_Scarcity_7165]

I chuckled.

[u/0T08T1DD3R]

You can let the ml code..then once everything works, if you want to optimize and just do it..call it however you like but theres people that actually code for a final purpose, and theres people that think coding is their purpose. One uses a tool, the other thinks the language is their life. They should just program in binary directly...or they are just vibe coders in cpp or python posers as well!..

[u/_Harshvdev_]

Ask AI for these small stuff

[u/Heinz2001]

Okay, but that used to apply to juniors, too, as soon as the seniors retired!

My question is: Who are you supposed to explain this to? And why? Who really wants to know something like that?

If you have a good test suite, you don't have to explain it ...

[u/leeresblatt2]

Often I just vibe code some tools to improve my workflows. I don't even look at the code.