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 @Tijn @baldur I do get your point. And yet, there seem a few things are very debatable here:
1. To try and divorce the work of an artisan or artist from the care and devotion it took to make it, gives a way the impoverished USamerican materialist. It makes no sense to anyone else.
2.if you can't find the space to put effort and love into making something meaningful and beautiful, may it be a work of art or the relationship to your kid, something is fundamentally wrong in your life, something AI can certainly not fix and you should do something about it .. And if it's systemic, well, start a revolution then, I guess.
I'm kind of just debating for the sake of it. I have heard of this argument but its definitively a non starter with me. It's a symptom of something much more deeply wrong with the US culture in my eyes. And I know about stress and not having time. but sorry . The value is in the devotion. In the creativity.That's where the beauty is being born. No shortcut to that.
This reminds me of how scary the US culture was to me, when I visited.
@Tamtam @Tijn @baldur I don't entirely disagree with you, but I also don't think rejecting the collapse of civilization to slop can be something we predicate on getting people whose minds are stuck in USian materialism to change their worldviews. Not because they don't need to change, but because that kind of change takes time and we are exploding the amount of harm our systems are doing right now with "AI".
@dalias @Tijn @baldur fair.. I just wanted to add a perspective from outside the US.
@dalias @Tijn @baldur And the scary thing is not the culture. It is the fact that "culture" is something that's roped of and bought and sold. And not part of everyday life. And the huge void that that leaves. That feeling of total emptiness is a shock to the system. And it gripped me right when I stepped of the plane. Not that that is not happening in Europe. But the US is just so much furhter down the road.
@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.

@dalias @Tijn @baldur I think this framing is a sort of victim blaming. It is not the individual developers who must love and care about the craft. It is the organizations who must mandate, validate, and ultimately incentivize quality. When all funding for architecture, design, QA and maintenance are cut and everything is left to the developer it is an organizational failure, not an individual one. I don’t need my plumber to love their craft, I just need them to follow code and pass inspection. I do agree that this was a problem long before LLMs came along.
@pier @Tijn @baldur I think you're saying exactly what I was trying to say. As someone doing a job you don't have an obligation to love and care for the craft. But the organization you're working for has an obligation to make sure you pay all due attention to safety of the things you produce and to design the process accounting for the possibility that you might fail to do so. Not to incentivize you to cut corners or look the other way when you do.
@dalias @Tijn @baldur Yeah I was meaning to reply further up the chain; I find threading in Ice Cube a bit goofy. I agree with everything you said. I’d even take that further though and suggest that major software platforms that impact significant portions of society should be way more heavily regulated, along the lines of utilities or banks. Relying on an organization to enforce quality when all of their incentives push towards “move fast and break things” is going to be a losing play.