3 ms·
Risk is always an interesting thing to consider in software, especially with complex systems. Let's say there are two bugs in our banking code. Bug A means tha
by braythwayt 7y ago
Risk is always an interesting thing to consider in software, especially with complex systems.
Let's say there are two bugs in our banking code. Bug A means that every once in a while, it fails and a user can't log in. Bug B means that the system always works, but every once in a while, it shows an incorrect balance on an account.
Hmmm... Which one is worse?
Well, that depends. Obviously B is very bad in some very obvious ways. But A could be catastrophic if one of the system's uses is doing something like making payroll for hundreds or thousands of people.
Hmmm...
- vinniejames 7y agoSure it's something to consider. But what's worse...a system that may have minor bugs while upgrading; or one that lets low level criminals easily swindle the system for millions on an everyday basis?
- braythwayt 7y agoYou’re right, we can’t let low-level criminals swindle the system, we need that money for the really elite criminals running our multi-year system modernization IT projects. /ducks!
- perl4ever 7y agoWell, there's always been a huge difference between predictable small losses, and unpredictable ones with no limit. Variance matters a lot. Millions are negligible if you're processing trillions and the losses are shared by everyone.