upvote
Basic competency is going down. Everything is outsourced such that no one knows how their critical systems work.
reply
Competency going down, timelines being rushed, project managers and CTOs forcing new tools at breakneck speeds.

i'm all for experimentation and adding new tools when they're shown to actually help, but it seems like large software companies (especially banks and e-commerce) just don't care about quality anymore.

reply
I think quality of most products is seemingly going down. To me it is a likely consequence consequence of increased financialization and money being expensive.
reply
Contrary to "vibecoding" (which is increasingly becoming how anyone programs) being a cause or consequence, it'll probably be part of the solution.
reply
> Contrary to "vibecoding" (which is increasingly becoming how anyone programs)

Commonly asserted but not true. Most programmers are not just letting the model take the wheel.

> it'll probably be part of the solution.

LLMs can't solve the slop problem they themselves are creating.

reply
> Commonly asserted but not true. Most programmers are not just letting the model take the wheel.

In what way did you interpret vibecoding as taking the wheel away from programmers? It certainly does in writing code. Generally developers are still involved in architecture design and defining requirements to give their agents.

> LLMs can't solve the slop problem they themselves are creating.

Human slop is the real problem that LLMs can and are solving.

reply
I worry that this isn't the right metric for diagnosing whether there's a problem. I'd argue that we've had instances in the past where a massive increase in how accessible programming is ended up being a net gain in the long run for software even if the average quality went down (e.g., having computers move from giant room-sized mainframes that only companies and governments could afford to sitting in the living room on a table probably reduced the average quality because untrained amateurs could start write software even if they weren't skilled enough to be employed). I could potentially be convinced that this isn't the same and that it will end up being worse for software in the long run with a stronger argument, but "software quality is going down in general" isn't convincing enough evidence for me.

All of this is also downstream of what I think is even more important, which is what's better for society in general. Obviously low quality software is not better for society than high quality in a vaccuum, but I also don't think there's a single obvious objective answer for whether the influence of software on society is a net positive or negative today compared to, for example, when computers were all mainframes and all software was produced by people paid to write it. There are a lot of differences in society today compared to back then, and software certainly has some role in how we ended up here, but trying to attribute exactly what and how much is not an exact science.

This is a lot of words to basically say: if you're confident that this is a problem, I think it's important to state exactly why, since I think the interest parts of the discussion are in how you've concluded that.

reply
Here's my “favorite” chart showing the steady decline in software quality over the last 25 years: https://trends.google.com/explore?q=%22something%20went%20wr...
reply
That's more like the rise of Google (which may or may not be correlated to software quality), as "something went wrong" is an error message popularized by them.
reply
Software quality peaked between XP SP2 and the victory in the market of node.
reply
Very well put, your comment alone should probably be a dedicated post in here with people commenting on that timeline (people who were actually programming back then).

Maybe it was because I was a lot younger back then and a lot more idealistic, but especially for the ~2005 (i.e. just after the dot-com crash) - 2010 period (just before money would ruin everything in this industry) I can say that the programming bar was placed a lot, a lot higher compared to where I see it placed now. Software wasn't perfect back then, of course, but there was a real push (belief, maybe?) that with enough will and with enough new-knowledge-being-acquired then we (meaning all of us as an industry) will make things a lot better. In part the existence of this very forum is a simptom of that philosophy, what if it (originally, maybe it still is) being written in Arc, or Reddit originally being launched in Lisp.

reply
Maybe node software was good initially, but its model was unsustainable, it relied on outsourcing to volunteer programmers, relying on such programmers means increased vulnerabilities, supply chain incidents, and low quality of software.

Vibecoding is an extension of the culture of overrelying on massive external dependency graphs. It's a preference for visual confirmation that something works and a disinterest in how it works. I think it's also related to the tendency of content feeds that are based on likes and swipes instead of searches, instead of specifying what we want, we are reduced to approving or dissaproving (until we are removed from the loop entirely)

reply
considering how the experience with most SaaS products right now is insufferable with broken states and UI, I imagine the same broken behavior is leaking in every other area of product development, so I agree
reply
Source = trust me bro. What’s that bias where things are so rare that when they happen it makes news, so you think they’re very common (eg plane crashes?).

Uptime and quality of software is about 10000x better than it was 10 years ago. Things just work all the time now.

reply
Also, source = trust me bro? How can you make the opposite claim without backing it up either
reply
> Uptime and quality of software is about 10000x better than it was 10 years ago

Extraordinary claims require extraordinary evidence. You're being the 'trust me bro' in this situation.

reply
I'd argue that just illustrates the point that it's impossible to have an interesting discussion without a stronger claim from the parent comment. If I say something that's too vague to falsify, and you can just as plausibly claim the opposite, you're not at fault for failing to turn my claim into a more rigorous one.
reply