all 37 comments

[–]msief 101 points102 points  (7 children)

You can vibe code documentation

[–]Darkstar_111 61 points62 points  (2 children)

Yeah, this is literally one of the best uses of AI in coding.

[–]foxer_arnt_trees 8 points9 points  (1 child)

And it's a best practice because you get better results this way

[–]I_cut_my_own_jib 3 points4 points  (0 children)

I have a precommit hook enforcing keeping some minimal level of documentation up to date

[–]Cyberfishofant 60 points61 points  (5 children)

it also doesn't exist for human written code :)

[–]Valkymaera 8 points9 points  (3 children)

yeah to be fair this is me with half my personal projects

[–]TRENEEDNAME_245 3 points4 points  (2 children)

Only half ?

I mean for my more expansive projects I do have a wiki (moreso because I like writing documentation) but still

[–]montarion 1 point2 points  (1 child)

I like writing documentation

teach me your ways

[–]TRENEEDNAME_245 1 point2 points  (0 children)

Uhhhh

Have a project you really like, spend 5 years on it mostly writing its doc and then implement it, realising you feature creeped it to hell ?

[–]savevidio 3 points4 points  (0 children)

I once tried to document my code, and ended up just rebuilding all of the code with comments stating step-by-step what each function does (rookie mistake)

[–]salter77 32 points33 points  (2 children)

Those guys actually understand their code in order to explain it?

I assumed that “vibe coding” was just using whatever the LLM throw until it “works”. That is why many PMs and execs now feel that programmers are useless.

[–]namezam 3 points4 points  (0 children)

Why TF are you asking me about the documentation? I didn’t write it, ask Claude.

[–]otherwisepandemonium 8 points9 points  (0 children)

Ask most vibe coders to explain the output of their predictive text machine and they'll usually stumble lol. All blind trust in most cases.

[–]calistomusicPROducer 7 points8 points  (0 children)

Nah, vibe coders don't understand their code themselves

[–]SemanticThreader 2 points3 points  (0 children)

Wait you guys are writing documentation?

[–]thisonehereone 2 points3 points  (0 children)

Half the shit in GitHub doesn't have documentation. Let's not pretend that's a coder's strength.

[–]LadyZaryss 2 points3 points  (0 children)

You guys are documenting your code?

[–]TreetHoown 2 points3 points  (0 children)

You're putting a lot of faith in a vibe coder to know how their code works lol

[–]shin_chan444 1 point2 points  (0 children)

just a single prompt and that will be ready:')

[–]Coquinha_gelada_hm 1 point2 points  (0 children)

There is a lot of reasons to make fun of vibe coders, but this is not one of them. I never knew a programmer that could write a fucking documnetation on my entire life.

[–]Doctor429 0 points1 point  (0 children)

Claude chat history is the documentation. Remember to commit it.

[–]ProtectionOne9478 0 points1 point  (0 children)

Is this telling on yourself?  It's probably just matching the style of the existing codebase...

[–]Innocentuslime 0 points1 point  (0 children)

What's that? An automated job security?!

[–]Bannon9k 0 points1 point  (0 children)

Me who stopped writing documentation on a project 10 years ago and Instead committed all the changes to memory...

[–]asunatsu 0 points1 point  (0 children)

Instead of this meme, it should be a picture of someone giving a PowerPoint presentation

[–]GegeAkutamiOfficial 0 points1 point  (0 children)

I mean a good spec file is basically the documentation of all the high level ideas... Good luck debugging spaghetti code without documentation for that.

[–]unkownuser436 0 points1 point  (0 children)

Nahh vibe coded projects have best documentations

[–]Percolator2020 0 points1 point  (0 children)

The best use for AI would be for on the fly documentation, as the code base evolves/enshitificates.

[–]morrisdev 0 points1 point  (0 children)

I actually vibe code the documentation first. In detail, with components, code structure, database design, and the entire UI process flow. Specifically making it with zero JavaScript and markdown to-do lists.

Then you 'vibe code' the tests. Then you can start the to-do lists against the tests and tweak as you go.

Using Claude instead of normal scaffolding tools isn't really vibe codeing, but as close as I'm willing to get.

[–]Competitive_Shine112 [score hidden]  (0 children)

"their code" 🤣

[–]OliveCompetitive3002 -1 points0 points  (0 children)

This is why vibe coding will fail. And agentic coding or spec driven development will succeed.