The
programming equivalent of the driving condition
road rage.
Code rage occurs when, having stumbled upon a pretty
nasty problem,
frustration sends the
programmer into a
frenzy usually consisting of the following two steps:
a)
tracing through the
program using a
debugger to find exactly where some
value screws upb) creating a
makeshift hack and
praying it solves the
problem as a whole.
Of course, step b never solves the problem as a whole because of the other major characteristic of code rage: it is
5 A.M.
The beauty of code rage, however, is that it is a forecast of
good things to come--as soon as said programmer awakens the next
morning, the
real solution will lie comfortably in his/her brain, a mere
compile and
link away.