I'm trying to track down a blog post that I vaguely remember from back in the day—probably at least 10 years old, maybe more. It discussed how fragile all technology and the internet are, pretty much describing it as a house of cards. The idea was that it only stays up thanks to the hard work of sysadmins maintaining decades-old code. There was also some mention of how people often don't see this as 'real work,' contrasting it with something tangible like digging a hole. I'm not sure I have all the details correct, but I'm really hoping someone remembers this post and can point me in the right direction. Thanks!
4 Answers
You might be thinking of this xkcd comic, which captures a similar sentiment about tech's fragility: https://xkcd.com/2347/ But if that's not it, let me know!
That's what immediately came to mind for me too!
I know this comic, but it's not quite what I remember either.
Although it's not the specific article you're looking for, I thought you might find this relevant: https://web.cs.ucdavis.edu/~rogaway/classes/188/materials/the%20machine%20stops.pdf It dives into themes around technology and dependency.
Good read, but also not it. I appreciate the suggestion!
While it's not an exact match, check out this article: https://www.computerworld.com/article/1555366/opinion-the-unspoken-truth-about-managing-geeks.html It touches on some similar ideas about managing tech and the unseen challenges. Not sure if it's what you're looking for, though!
Author of that article here. No, it's not what you're thinking of, but I get what you're saying.
Sadly not it, but thanks for sharing!
This is definitely a recurring theme in software development. Most products are built on the foundations laid by previous developers, which can lead to some serious complications if no one acknowledges the underlying issues. You can see it reflected in the constant flow of CVEs that come out. It's definitely a double-edged sword when you're relying on past work without recognizing the risks involved!

Not sure this is what OP meant, but it would have been my answer as well.