All the devs saying that Anthropic’s code quality is “normal” are telling on themselves and everybody they’ve worked with

(Also supports what many have been saying about software quality being a crisis that precedes LLMs, but that’s another story)

@baldur the software crisis is definitely what enabled vibe coding, I feel.

When making software was an artisan process, it was hard for corporations to scale it and treat programmers like cogs in a machine.

So they've been trying more and more to fit software development into a neat mold, essentially dumbing down the process, to the point where making an app has become "just slap together some libraries and hey presto".

That has 100% laid the foundation for LLM-generated code, I feel.

@Tijn @baldur "Artisnal" is not the word I'd use for making sure a bridge or skyscraper doesn't collapse. Software is an equally safety-critical endeavor in most places it's deployed and the reason it needs to be done there is respect for human life and safety not respect for artisans.

@dalias @baldur Yeah this is fair imho!

What I was mainly trying to convey was a sense of caring about what is you're building as a developer.

That's the thing that's lacking imho from corporate coding practices. The workers don't have to care about the software, they don't have to understand the whole thing, they just need to solve the ticket and move on.

This mindset fundamentally undermines the quality of any software project. And also perfectly lays the foundation for LLM-generated code.

@Tijn @baldur Yeah. I just think if you're working for an employer on a project that will affect the public, the way you should be expected to care is the way an architect or engineer working on physical infrastructure is expected to care, not the way an artisan/crafter is expected to care.
@dalias @Tijn @baldur one momento Are you an artesan? I 'd think they possibly care just as much. In exactly that way.

@Tamtam @Tijn @baldur The reasons for caring are different. I care for both reasons in my work, but I think it's somewhat elitist to demand that, in order to work in this field, someone has to view it as an artisnal craft.

Someone can reasonably view it as purely a job, but still respect that it's a job where people's safety is on the line if they fuck it up.

The reason I bring this up is that too often, when we just focus on the artisnal aspect, the pro-AI and AI-curious crowd sneer at it as they would if we were expecting everyone to buy handmade furniture or hand-sewn clothing - fields where there is certainly a reason to respect the artisnal element, but where nobody's safety is on the line when you don't, and where most business-minded people aren't going to respect it.

@dalias @Tamtam @Tijn @baldur not every software project is load bearing or essential but unfortunately we allow the practices of those that aren't to dominate the industry

@McNeely @Tamtam @Tijn @baldur Not every software project is, but basically any public-end-user-facing software deployed commercially is, because it's dealing with private data pertaining to the user that could endanger the user if it gets in the wrong hands.

This *shouldn't be* how it is. None of this software should be phoning home, outsourcing operation to cloud services, etc. But that's the way it is now, and as long as it's like that, it needs to be regulated as load-bearing, safety-critical software.