Redundancy++ … this is one of the topics on my writing list, mainly because I didn’t feel like writing about other topics today.
I always thought the difference between the two programming languages, C and C++, was that the “++” made it somehow better, like it it was the successor to plain ol’ C sharp (C#). It’s quite the contrary, and you can learn about that here. Nevertheless, I thought Redundancy++ looked like a neat title, so here we are.
In The Wonderful World of Web Development, you’ll always encounter one question, “what’s your backup?” Maybe it has to deal with a new feature release that might only be rolled out to a select group of people, and you need a contingency plan for when things go south. Maybe it has to deal with offshoring your boatload of data, and the various processes that will take into effect, in case of some random outage. No matter what, you’ll always have Plan B lurking around the corner.
Whenever I work on something, I tend to think of the many different ways I can accomplish that one thing. Usually, there’s a great way, a good way and a hacky way to do that thing. In all cases, that thing will somehow get done in some way with the “great way” clearly taking the lead. But instead of throwing the other two ways away, those become my backups. In many cases, I’ll even start on them a bit just to validate that they are indeed good and/or hacky yet functioning. That way, I already have two redundancies in place. It’s the equivalent of more upfront work and having less of a headache when something crashes versus working on a coronary while something is crashing and you don’t have a backup plan. Good times.