I feel like no one has said the elephant in the room.

QA teams were fired/never hired in the first place (put onto the Devs/support/customer to report and test)

Management want features and selling not Lovability and polish. We are just hitting an all time of make make make.


This is the correct take. QA was under attack the entire Agile(TM) cycle we just exited. Now with agentic coding, the only thing keeping it on the rails is TDD. Either you write the tests or you write the spec.

You are also responsible for the output. Welcome to the New Age. Management is just as clueless as they have ever been (some more than others) and yet most of them lack the intelligence to know exactly how it all works. Hell, there’s still plenty of engineers that don’t know how it all works.

Eventually, when you come to understanding or you reach that “enlightenment” stage, no corporate BS will penetrate you and you’ll forever see past their shenanigans. At this stage though you’ll be a grey beard and be unemployable. So they cut out anyone who knows the BS to bring in folks who believe the BS so they can continue shipping BS.


I agree with most of what you said, but this...

> At this stage though you’ll be a grey beard and be unemployable.

isn't as true as people think. I'm a graybeard and remain very much in demand, as do the majority of the graybeards I know.


I thought about writing a comedy, set in the far future, where everything looks beautiful but nothing works right and it's just accepted (almost unnoticed) as a running gag throughout the film. Now I wonder how prescient that would be.


Also there is trouble with back end IT systems. Like I had some trouble with my homeowner's insurance which was initially my fault [1] but my insurance agent was gracious and helped resolve it and my wife paid her right in her office. Then they do some software update and in the process cancel my policy and I get a letter from my lawyer [2] wanting to collect $82.54

[1] although if I was trying to design a spell to make people not pay their bill I might try sending them 20 letters that say THIS IS NOT A BILL before they get the bill

[2] who is also their lawyer


I guess things keep getting more features and complexity but all of it is 80% done because it's "shippable" and updates are cheap.

This is most visibile for me on Windows/MacOS and complex web apps (e.g. GitHub and GitLab, including consoles of hyperscalers), where 80% of "normal" things work, then you need the last 20% and it's always not working as documented, only half-working, or just outright broken, and you need to find "temporary" workarounds that stay in place for years.

I feel this is being amplified by AI: tests come last (if at all) and are still written by LLMs, nobody really looks at them anymore, green pipeline checkmarks mean less than they did in the past.


I feel it in two ways.

I've been using windows for the past 5 years or so. I was using Linux before that. I used to complain about things breaking in Linux but the situation in Windows is way worse than it ever was in Linux. A couple of days ago my co-worker turned on his computer and windows has locked him out somehow. He had to disable secure boot, recover his bitlocker passphrase from his microsoft account, and only then could he get past the boot screen. The theory is that his laptop turned off while updating. I'm thinking, why doesn't the update abort when it realizes it's not plugged in or on low battery. He said it had never happened to him before and I have also never seen it.

The other side I notice is with google products. Barring android, GCP, and the less than yearly occassional outage, I would never see a bug in google products. Now I notice them often in drive, sheets, gmail, and specially meet. The other day I joined a meeting and all participants couldn't log in. NEVER have I seen such a bad production bug from google.

Profits over wonderful products I guess


My two Win 11 machines have been pretty solid for a while, but my Ubuntu Linux machine has had a lot of trouble with software updates.

When I built the machine about 12 years ago [1] it allocated a /boot partition that was big enough then but not big enough but as Ubuntu grew the /boot was too small to keep as many versions as Ubuntu wanted so kernel upgrades needed manual intervention. And for that machine it is a hassle because it runs headless and if it doesn't come up with the Ethernet working I have to pull it out of it's home and set up a workstation.

More recently I rebuilt / completely (kept the ZFS array) and this time Ubuntu didn't make a /boot so the files live on / but now when it does software updates it often fails to install the realtek driver modules so it comes up without the Ethernet and I have to take it upstairs to rebuild it. Copilot offered me a script to tell if the modules are busted after a kernel upgrade so I can do the the manual fix before the reboot now.

I guess I can't complain too much, I mean this $150 machine that I upgraded with 32GB of RAM and a NVIDIA GPU is going strong, though now that I think about it the second ZFS array I built for it is past warranty even if it only half full.

[1] I know because I named it after my favorite vixen from a video game I was playing back then


Yes. My observation is that FAANG culture persisting the myth that testing is slow or writing clean/consistent code is slow (conveniently playing to the dev's ego, but I digress). As a result, a lot of bugs get shipped, inevitably triggering a rework cycle. But what does not get measured, does not get reported. As a result devs look busier than ever, great for their reviews, while quality dives.

A turnaround in the industry would be actually capturing the rework cycle into costs.


My running joke for the last couple years is "Nobody knows how to write software anymore" (even about a bug in my code). The problem is almost certainly complexity. Apps are like a house of cards, and we keep adding to the stack with new features, external dependencies, etc. My apps 30 years ago used one language, one library, one process, one thread and shipped on one platform. Now it uses Java, JavaScript, CSS, HTML, SQL and has a dozen linked libraries, talks to a couple servers, has dozens of threads, and runs on desktop, browser, tablet, phone and car console. It's a wonder anything works at all.


I don't know about just the past 6 months, but past 10-20 years, sure? I think software today has to handle much more varied and complicated I/O at a much bigger scale than it did in the past. Website UI/UX has to accommodate not only numerous browsers, but numerous devices with different viewing spaces. Think of how much broke when Python was rejiggered to not implicitly typecast unicode data. Think about all the legacy databases that can't handle spaces or various non-alphanumeric characters.

The userbase for software in the early 2000 was built for a much, much smaller audience than it is today. And I'm not sure the huge improvements in testing/debugging and general software development would totally mitigate that, in the same way modern military defense systems is still way behind modern offensive weaponry.


There has been a steady decline for decades. Release early, release often. One example: Apple used to have a thing called Gold Master release when updating software was not as immediate. The GM programs met a high bar for quality. Not so much anymore… the attitude is we can just release a new version later this week. There also used to be a thing called backwards compatibility… now no one thinks twice about breaking code on older platforms.


I use cheap android devices. My current one is a cheap Motorola and before samsung and Chinese vendors. I've never seen bugs like I have encountere since the last update (2 months ago).

Unless I reboot the device everyday, I can't make a call. The button is pressed but never proceeds to ring, doesn't even show an error message. The play service complains that I am logged out but shows my account info in the login panel!! Rebooting is the only way, android is like windows currently.

I am just scared to update anything these days. And not just android apps, Even rsync gave me a minor scare (fortunate my backup jobs are on debian stable).


It's similar to the ElectronJS desktop app problem. Sure the desktop apps use a lot more system resources, but it's doubtful those apps would have been created in the first place if it wasn't for the speedup of development allowed by ElectronJS.

In this case, sure software is buggier, but there's also a ton more software+features that wouldn't have existed before AI coding tools.


Electron apps are selected for things that are harmful to your user experience.

That is, if you know how to make Electron apps you also know how to make web applications and web applications are generally superior and preferred by users. No install, no bloated runtime, "just works", say it again "JUST WORKS!"

Any time somebody makes an Electron app there is a reason why they make an Electron app and it usually is a bad reason. For instance, Electron apps can live in your tray and make your computer harder to use by hiding behind twisty little icons that all look alike, popping up and covering other things that live in the tray, etc. Defying the usual procedures for starting and stopping apps, finding and moving windows, etc.

And of course the whole point of living in the tray is running all the time, sucking RAM all the time, sucking CPU all the time, sucking GPU all the time, sucking network bandwidth, etc. In short, sucking.


I mostly feel this on Microsoft stuff. O365 browser stuff was always buggy, but last month I had to fight to zoom in on something in PowerPoint. Pagination in Azure ML randomly broke, it took them a month to fix it.

Atlassian is also a bug factory, but I did not expect anything better of them. Each UI update they did to Confluence and Jira just made everything more confusing in the last 10 years.


Holy smokes is the browser versions of PPT, OneNote, word etc buggy, I could not believe that was an actual released product. Random page crashes, refresh loops, etc, all for the crime of using firefox on a mac. The bottom of their test matrix sure, but not exactly netscape on windows XP.


Someone should come up with an index to track this objectively.

Otherwise, its all anecdotes and speculation.

Some random ideas:

1. Measure trends in HTTP status codes over time

2. Measure github issues created over time

3. Measure complaints on forums over time

4. Google trends


We've always had bugs. Good chance that it's largely confirmation bias - you're familiar with how software development has changed in the past 6 months, and especially if you don't like it, any time you see a bug or a problem, you'll attribute it to that.


I think software has always been terribly buggy. Back in the day, things would crash (including your entire OS in many cases) all the time. These days, it's more often smaller, stupid UX issues, but that's been the situation for a few years. I've seen no difference over the past six months.


It's definitely been buggier for a while now. It's already been an issue for a decade or so due to the "release minimum viable product, fix problems with patches/updates model" (especially in the world of video games), but the rise of AI has only made the issue more apparent. Microsoft is the biggest example here (with Windows 11 seemingly screwing up something massive in every update), but other companies like Google and Meta haven't been as reliable either.


I had one encounter with an obviously vibe coded website last year. Everything looked great, but nothing worked. Had to deal with the company over email.

Things might be better now, but that was a clear warning of what future may hold.


"weak computers" is the funniest part. The computer I'm typing this on *right now* is orders of magnitude faster then the Athlon XP processor that i was using in 2003, but it doesn't feel much faster. I think that hardware advancement is just slower then software bloat...


I think gstatic.com was down yesterday or something because a ton of websites just stopped working.

Spotify on Android got an order of magnitude slower recently.

These are just the examples that come to mind that I've dealt with from the last 48 hours.


Not only buggier, but less usable overall. We can not blame everything on AI. For example events discovery platforms and ticket platforms were way better decade ago, you could search by popularity, friends going to the same event and there wasn’t as much fragmentation. That part you could blame on Cambridge Analytica scandal and late capitalism love of algorithmic feeds


It's pretty hard to separate this from confirmation bias. But I've had to disable the YouTube app and switch to mobile web because it would just buffer nonstop on everything; never had issues like with it like this before.


Websites and mobile apps, definitely. Every time a typical proprietary mobile app updates I wonder what they will break. They always do break something or remove a feature I want.

Desktop apps, not in general. Some work better, like KDE's DE has fixed some irritants.


Yes, I initially jumped from Android to iPhone back in 2019 or so because I felt like the experience was much more stable and it just worked, smooth, no issues, kinda boring but in a good adult way. Now every interaction makes me want to throw the phone out the window. If it’s not just blank, the keyboard doesn’t come up, the navbar in Safari sometimes is there, sometimes it’s a blank rectangle, etc. “ask your developer to update the apps to run well in iOS 26” is such a garbage response. We didn’t need to break everything just to have some glass simulations that make everything slower and add no value.

Google Home: holy shit dude. It was a mostly working thing. Absolutely unusable with Gemini. Will get the transcript right 15% of the time. Can’t even ask for the weather.

Roku: Netflix playing in the background but I’m still in the main menu.

I can go on


feature velocity >> feature stability.

Core libs/software have never been better, eg I have had much better luck with stuff like ffmpeg and virsh than ever before.

If it has a UI and targeted at consumers though? Bug city.


iOS is definitely buggier. It used to be a silky smooth experience but it's degraded significantly in the last year or so. Safari on iOS, in particular, is very bad. Lots of problems in Adobe Creative Cloud on Win 11 (primarily Photoshop, InDesign, Illustrator) in recent months too.