Member-only story
The Biggest Single Point of Failure are Developers
How development teams can create weakness
“Success is stumbling from failure to failure with no loss of enthusiasm.” — Winston Churchill
Good software design avoids a single point of failure because it creates a weak point in your design and if it fails, the entire system will stop working.
Considering murphy’s law and probability, we know at some point it will go wrong. It’s a matter of time until at some point this will stop working — You Cannot Create Software Without Bugs, Problems and Mistakes.
In your technical solutions you can have backups or with online services Microsoft will deal with the redundancy and, in the background, spin up other servers. This will mean the service will have a small delay but will be up — like a weebl. You knock it down, but it pops back up.
The single point of failure developers miss is the developers and their knowledge. I’m sure you have worked on a project where only one developer knew how something worked and no one else could do it.
There can be one developer who has the technical skills, knowledge to fix something that no other developers can fix.
