-91
do we need documentation in the age of AI?
(thelemmy.club)
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev
"You're not using the latest model", "You're holding it wrong", etc...
It's the same shit, different day.
I'm consistently told LLM generated code is the best thing since sliced bread, and people keep handing me "proof", yet every time I open what they've handed me, I see a shit sandwich.
And as soon as I point that out, the goalposts are moved yet again, ad infinitum.
I think the effect you're seeing is that different people have different levels of "good enough", and also they work in different domains where AI became good enough at different times. E.g. for one-off web page design it's been good enough for a long time.
I never said this for earlier models, because they did suck for things like Rust and SystemVerilog. Now they don't.
I'd share some things I've vibe coded that work basically perfectly but they're linked to me real name, but you could have a look at the Mold linker which was recently vibe-ported to Rust.
You do understand that this is a rapidly developing technology right? That it's getting better weekly?
It's clear you have no idea what you're talking about. You can't just bury your head in the sand and tell yourself that LLMs are still just "advanced autocomplete" anymore.
This is literally the retort that moves the goalposts.
I made no claim that LLMs haven't changed, I make the claim that others are making claims that fall apart once examined.
The claims others make:
AI is amazing because now it can make this thing
Oh, the only reason doesn't hold up to scrutiny this one time is because of {insert goal post moving here}.
Argument 1 falls apart when looking inside the product (i.e. the shit sandwich, the slop grenade, etc...).
Argument 2 is circular, so I'm not going to waste time on it.
But just for the sake of argument, lets say there's some sudden release of a model tomorrow that runs one million times better than today's best model and everyone only uses that model from now on. Will I still be handed a shit sandwich?
Yes.
Why?
Because the fact that I'm handed a shit sandwich isn't influenced by how good the model is. It's based on the fact that English is a terrible language for logic.
We discovered this in the 60s and 70s. Computer programming was too hard in the 50s and only getting harder, so everyone got together and tried to make a programming language out of English, that way everyone could do it. That's literally how the Cobol language came to be. It was sold to everyone on the idea that anyone could create something with a fuzzy human readable language called English.
What did we learn? English is both a terrible programming language and a terrible specification language, Non-programmers (managers, general workers, etc...) fall prey to things like the xy problem, understanding gaps, intention gaps, etc... and so can't end up with a new good product by giving orders. The scars of that delusion are still felt in our banking system today. Every lesson learned by Non-programmers in the goal of getting a good program turns them lesson by lesson into programmers, and at that point you're just programming by hand anyway.
The same lessons were rediscovered in the 80s by people trying to program by spreadsheets and GUI-only app builders, the 2010s with the no code movement, it's currently being rediscovered in the 2020s with LLMs, and it'll be rediscovered again by a new generation in the 2040s once those with the experience and learned wisdom of last time retire out of the industry and the few remaining are outnumbered and dismissed as religious zealots.
Literally not moving the goalposts.