Very experienced software developers can be incredibly deluded about the quality of vibe coded output esp. for large scale feature work - see the SBCL discussion on fibers https://sourceforge.net/p/sbcl/mailman/sbcl-devel/thread/CACxje5-Nwfoe8REix2B8KGksLi31OSW0A32LQbfCccrpM1R1%3DA%40mail.gmail.com/#msg59302483 - worth reading closely. A proposal/implementation that took a couple days to vibe now has no specific timeline to address all the issues raised by reviewers.
Thread: [Sbcl-devel] SBCL Fibers proposal | Steel Bank Common Lisp

@[email protected] the exact thread that led to my decision to drop SBCL and Lisp, I'm using Chicken Scheme now instead and am happy. (Chicken does accept vibe coded contributions in theory, I have not seen any commits though).
@brettm I don't see any cause to drop SBCL in that thread? But ok.
@swannodette @brettm If anything, the response from the maintainers was exactly what I'd like to see. They were extremely professional and engaged genuinely with the proposal while noting its flaws and poking holes. They are clearly not blindly accepting slop and are holding LLM-generated material to the same standard (if not higher) than human-generated.
@[email protected] @[email protected] ok but how about the planet-destroying llms that wrote the code, no concern for the hundreds of millions of extra people that will die due to encouraging all those data centres to be built and add and extra 20-30% draw on the world's power grids? Can't get much more professional than throwing humanity under the bus, I suppose!