Building in 2000
When I started my career back in 2000, the company I worked for had their servers in a bank safe kind of room.
There was one keyboard shared over several servers. You would have to unplug it and replug it into the server you wanted to administer if you had to be physically on the machine.
This might sound a little amateur, but this is how many companies operated before the cloud.
Back then there was a single point of failure: the server or the connectivity. If either went down, your site went down.
Building in 2026
We are so interconnected now to so many third-party apps and services that during a normal work week I personally come across one of these going down or slowing down, thus stopping my workflow.
It could be Claude Code. Today it is Apple and building mobile app assets, along with the third-party site I use to build the images to deploy because I am on a Linux box.
The interconnected world is quickly becoming an interdependent world, which means your project could rely on multiple services being available and not going down for it to function.
At scale this becomes a risk where you could be doing everything right but someone else is letting you down.
Maybe the old days weren't so bad after all.
Originally posted on LinkedIn.