I ran into a similar case recently, there was a ticket describing what needed to be done in detail. I was written by a human and it was a well written spec. The problem is that it removed some access controls in the system, essentially given some users more access than they should have.

The ticket was given to an LLM, the code written. Luckily the engineer working on it noticed the discrepancy at some point and was able to call it out.

Scrutinizing specs is always needed, no matter what.

There's nothing wrong in being nice and some chit-chat. Any kind of work, well most kinds of work, are about people and relationships. Building something with people when people can't relate to one another is quite hard.

Open source book dedicated to helping you to make the best possible sourdough bread at home.

Oh thanks, this is a pretty good elevator pitch, now I see the connections I was missing.

One of the down sides of Vibe-Coded-Everything, that I am seeing, is reinforcing the "just make it look good" culture. Just create the feature that the user wants and move on. It doesn't matter if next time you need to fix a typo on that feature it will cost 10x as much as it should.

That has always been a problem in software shops. Now it might be even more frequent because of LLMs' ubiquity.

Maybe that's how it should be, maybe not. I don't really know. I was once told by people in the video game industry that games were usually buggy because they were short lived. Not sure if I truly buy that but if anything vibe coded becomes throw away, I wouldn't be surprised.

> It was the fast food of the chōnin class in the Edo period.

I definitely see that with C++ code Not so easy to "fix", though. Or so I think. But I do hope still, as more and more "modern" C++ code gets published

It is joyful. I think of it like a proof being written and that is confirmed to be correct (most of the times) in the end.

Thank you!