Software Development Faux Pas: The Code Fux

Software design and implementation is still very much an art. This is not surprising when you consider that mankind, with the exception of a few individuals like Charles Babbage, has only been writing software for about 70 years. That, however, does not excuse some of the faux pas made in the name of "Software Development".

We all know about the bug fix. This is when you rectify an existing fault in a software system. However, sometimes a fix is not a fix at all. How many times have you reviewed a supposed fix only to discover that the code base has taken a backwards step? This is what I call a bug fux - because it fux your code base. If you don't get what I mean, read that last sentence aloud... I know it's crude, but I think the term captures the emotion you feel when you discover a fux.

Uncovering a code fux (the general form of the bug fux) brings on many negative emotions. First there's the anger that someone would desecrate your code base in this way. Then there's the shifting of blame completely onto the individual who implemented the change. Then there's the arrogant manner in which you believe that you would never have fuxed the code in this manner. Then there's general disappointment and dissatisfaction you feel when trying to work out how to undo the fux and do the fix properly.

But you know what - other than the wasted effort - it's just code, so get over it and go fix it properly. Ain't software fun.