@mrrmot @KathyReid @daedalus

I've dealt with one project that was "vibe coded"… it was a comms driver for a copper refinery written in Python.

I helped get it into some vaguely working order (most of that was wrapping calls to a C library in a module using `subprocess`… because the original authors played fast and loose using threading using a non-threadsafe C library) but made it clear its future maintenance would be their problem, not mine.

I've walked away from that project now, and will walk away from future ones of that nature from now on.

Code written by an uneducated programming beginner is bad enough, but when LLMs get involved, it's an unholy mess of epic proportions.

@what @samiamsam @daedalus How becomes this cheaper? Working slowly just deliveres fewer parts per time unit, so one gets paid less per unit but longer. So, in the end it costs the same. Well, extreme rapid quality may mean a lot of overtime work which is more expensive or postponed other projects, but generally only speed is not a cost factor in my opinion. :)

But nice thought game nonetheless!