←back to thread

413 points martinald | 3 comments | | HN request time: 0.198s | source
Show context
vb-8448 ◴[] No.46198283[source]
It's not just about "building" ... who is going to maintain all this new sub-par code pushed to production every day?

Who is going to patch all bugs, edge cases and security vulnerabilities?

replies(4): >>46198304 #>>46198394 #>>46198683 #>>46200328 #
sdoering ◴[] No.46198394[source]
I happily got rid of a legacy application (lost the pitch, another agency now must deal with the shit) I inherited as a somewhat technically savvy person about a year ago.

It was built by real people. Not a single line of AI slop in it. It was the most fragile crap I had ever the misfortune to witness. Even in my wildest vibe coding a prototype moments I was not able to get the AI to produce that amount of anti patterns, bad shit and code that would have had Hitchcock running.

I think we would be shocked to see what kind of human slop out there is running in production. The scale might change, but at least in this example, if I had rebuilt the app purely by vibe coding the code quality and the security of the code would actually have improved. Even with the lowest vibe coding effort thinkable.

I am not in any way condoning (is this the right word) bad practices, or shipping vibe code into prod without very, very thorough review. Far from it. I am just trying to provide a counter point to the narrative, that at least in the medium sized business I got to know in my time consulting/working in agencies, I have seen quite a metric ton of slop, that would make coding agents shiver.

replies(3): >>46198435 #>>46198564 #>>46198668 #
1. geon ◴[] No.46198435[source]
The argument isn’t that all slop is AI, but that all AI is slop.
replies(2): >>46198460 #>>46198468 #
2. ◴[] No.46198460[source]
3. baq ◴[] No.46198468[source]
Turns out building enterprise software has more in common with generating slop than not.