There’s not really any such thing as a one off web page.

Of course there is. What an absurd thing to say. A very obvious example is event websites, e.g. for weddings.

Why would you not reuse event pages for the next event?

Maybe it depends on the language but I’ve recently vibe coded two tools in Rust and I’ve skimmed the code and it’s perfectly good Rust. I would accept it in a PR - even if I was being as picky as I’d really like to be in reviews. I don’t think that would have been the case 3 months ago though.

I’d expect that the code would be almost exactly the same as other code that already exists, in which case, why not use that code?

I too love filling my code with things that silently reduce my understanding improving my code using stochastic prediction models trained on tainted data filled with hidden injection prompt attacks AI

For .one-off web page that is true

There’s not really any such thing as a one off web page.

It’s eventually going to need to be updated or reused for something else.

The only exceptions being if your company goes under, force majure, or if you have something with the same requirements but choose to make the same thing again from scratch for no real reason , which is just being inefficient and unreasonable.

Also the latest models don’t even make a mess any more.

Yeah… I’m calling bullshit on that, all four projects I was handed was made by the latest models and it will continue being an issue for the foreseeable future. (see a previous comment of mine for reasoning: https://programming.dev/post/57569685/26398217)

E.g. for one-off web page design it’s been good enough for a long time.

In just the last two months, I’ve been handed the following web projects:

• A page filled with bootstrap style div-soup
• A page filled with tailwind style class-soup
• A slideshow webapp that has duplicated state and three different ways to change slides (navigate(), goTo(), and changeSlide()).
• A slop-grenade of a chatbot interface for navigating a user through a flow chart, documentation of the flow chart, and documentation of the logic of the flow chart, all of which conflict with each other.

I think the effect you’re seeing is that different people have different levels of “good enough”

I think the effect that I’m seeing is twofold:

1. People don’t realise that every line of code is a liability.
2. People think that once they have something on the screen that looks finished, the project is finished. They haven’t thought about support or maintainability at all, and since they are completely inexperienced about such things: they aren’t qualified enough to when when a project is “even done”, let alone “good enough”.

“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.

That’s right, move those goalposts!