logoalt Hacker News

doug_durham • yesterday at 6:39 PM • 10 replies • view on HN

This narrative isn't consistent with reality. Cloud computing is much older than 10 years ago. We were doing production grade cloud computing over 16 years ago. The OSS revolution dates to the late 90's. The author seems to think that SWE was in a golden age 10 years ago. Sorry, but it's about the same. We have the same problems in SWE as we had 40 years ago. The scale and ambition of the problems we are solving have increased as compute capabilities have increased.


Replies

swatcoder • yesterday at 7:11 PM

The timeline is very confused, but the arc is mostly right.

1. Consolidating internet-dependent projects to a few winning cloud vendors and a dozen winning SaaS providers, made all of those project have coincident failure points. Which is great for corporate accountability ("it's Amazon's issue, not ours!") but bad for end users ("shit, EVERYTHING is down today")

2. The movement to migrate fat local-first projects towards thin internet-dependent or server-hosted ones made almost all software share those same coincident failure paths. This was good for entrenching a subscription business model and brought some end user conveniences, but meant everything being down meant everything being down.

3. Anxious and lazy dependency-first development culture ("you could never write that as well as some github rando") meant projects now had an order of magnitude more contributors but only reviewed and owned code for a surface level, making all these projects extremely vulnerable to supply chain failures and subject to constant maintenance churn.

4. Employment and team tenure continually fell so that most projects no longer have experienced owners and instead just temporary custodians.

You can find the seeds of many those problems in the 1990's and earlier and you can even argue that some of them were inevitable (and even worthwhile) destinations for the industry as it evolved without an engineering guild to slow it down and insist on rigor or evidenced safety.

But anybody who's been around for a few decades can attest to how these risky patterns rapidly grew into norms over the past 20 years and shifted the industry from one where any given software had some idiosyncratic bugs that users could learn to work around to one where all software had lots of bugs, many of them correlated across apps, whete failures would wash through and shut down (or make vulnerable) whole industries for hours or days, with effecrively nobody in particular to hold to account for any of it.

Software has never been in a pristine "golden age", but the last 20 years built almost everything on one giant, shared house of cards that's now teetering on the brink of collapse. Better or wose, it's indisputably different than it was before.

➕ show 7 replies
dreambigwrkhard • yesterday at 7:19 PM

Yes, there's too much to pick at with this piece.

The PHP2Shell bug existed more than 15 years ago, spanning releases as early as 5.x. There was no AI coding back then. So it's very hard to blame AI. There was a coding mistake, and AI found it in 2026. Probably a good thing before a malicious party does the same.

OSS definitely flourished way before 10-15 years ago. I'm not sure what the author suggests as "knowing the details". Should we all rebuild our own web scripting language to know "all the details": e.g. PHP? Probably not practical. A line has to be drawn on where your knowledge and expertise stop. THe line can be vague and consistently changing based on needs. But there will always be a line. We will always stand on shoulders of of our predecessors one way or another

I understand the author's trying to say the overall situation is unstable and trending negative but I am not sure the writing's logical flow is holding up very well.

A better way to put it is we've written a lot of code, and a lot of it had bugs hiding in plain sight. AI made the whole bill come due at once. And will this AI code explosion create another bill we won't know about until 20 years later? Who knows.

➕ show 3 replies
cmiles74 • yesterday at 6:49 PM

AWS is 20 years old, before that people did rent machines from places like Rackspace. Maven Central (Java) is 25 years old, RubyGems is 22 years old, CPAN (Perl) is 31.

I find the arguments about decoherence and the sort of snowball-of-complexity more compelling than this timeline.

➕ show 2 replies
paldepind2 • yesterday at 7:09 PM

I get the impression that when the author says "open source" they mean "rampant use of dependencies". And while the terminology is confusing and the time frame maybe not quite right, there certainly has been a shift where many projects went from depending on none or a few big reputable open source project (MySQL, Apache, Linux, etc.) into depending on hundreds of language packages made by random people.

Ancalagon • yesterday at 8:20 PM

Thoughts on the inter-connected bank outages today?

tyre • yesterday at 9:14 PM

Yeah when I read that the blooming of open source was in 2014 with NPM, I thought, huh, I sure remember using bundler before that and GitHub existing.

Reminded me of this tweet: “This has been talked about extensively you’re just 21”

Just because it is/was new to you at that time, doesn’t mean it is New.

d1algo12 • yesterday at 8:23 PM

This article is pure nonsense. Yes there may be more and more failures that are getting more difficult to catch and remedy in time but that is the nature of the kind of systems that we build nowadays and that is distributed systems at massive scale. When an error occurs in such systems the effect may show up in a far different component or part of the system and in multiple places effectively making it difficult to troubleshoot.

nullsanity • yesterday at 6:46 PM

[dead]

nosefrog • yesterday at 6:46 PM

Yep.