Redundant Coding: The new paradigm!
-
Today my esteemed coworker invented a brand new programming paradigm: Redundant Coding (tm). This buggy old legacy code we are working with has a least three almost identical and insanely complicated instances of a special form of coordinate transformation. We want to simplify, but which one to keep? My coworker suggested that we compare the results of the three code blocks too see which one, if any, would give diviant results. This immideately lead to the idea of letting the three instances "vote" on the right result. And BAM the Redundant Coding programming paradigm was born. Just as a jumbo jet has three of everything just in case, our code has three almost identical code blocks, just in case one of them is buggy! If one code block produces deviant results, the other two will take over! I am, of course, kidding. We will clean this mess up eventually.
Delphi4ever wrote:
Today my esteemed coworker invented a brand new programming paradigm: Redundant Coding (tm). ... This immideately led to the idea of letting the three instances "vote" on the right result. And BAM the Redundant Coding programming paradigm was born.
Sorry, that's as "old as the hills".. or at least, as old as the Space Shuttle. Three computers, each with software written by a different team of engineers (so the bugs are in different places) that vote on the result. Everything's working correctly when every vote is unanimous, but it can fly when there's only a simple majority. They scrubbed a launch in the early days because the votes weren't all unanimous. Now there's the way to use your backup systems :)
patbob
-
Today my esteemed coworker invented a brand new programming paradigm: Redundant Coding (tm). This buggy old legacy code we are working with has a least three almost identical and insanely complicated instances of a special form of coordinate transformation. We want to simplify, but which one to keep? My coworker suggested that we compare the results of the three code blocks too see which one, if any, would give diviant results. This immideately lead to the idea of letting the three instances "vote" on the right result. And BAM the Redundant Coding programming paradigm was born. Just as a jumbo jet has three of everything just in case, our code has three almost identical code blocks, just in case one of them is buggy! If one code block produces deviant results, the other two will take over! I am, of course, kidding. We will clean this mess up eventually.
One place I worked had five (count'em...5!) different memory management routines because "Microsoft's doesn't work." Really? Could it be you just don't know how to use it? Because that's going to be a big surprise to the millions of other programmers using it. But hey, when management wanted my opinion they told it to me.
Psychosis at 10 Film at 11