The 5 Stages of Debugging

The 5 Stages of Debugging At some point in each of our lives, we must face errors in our code. Debugging is a natural healing process to help us through these times. It is important to recognize these common stages and realize that debugging will eventually come to an end. Denial This stage is often characterized by such phrases as "What? That's impossible," or "I know this is right." A strong sign of denial is recompiling without changing any code, "just in case." Bargaining/Self-Blame Several programming errors are uncovered and the programmer feels stupid and guilty for having made them. Bargaining is common: "If I fix this, will you please compile?" Also, "I only have 14 errors to go!" Anger Cryptic error messages send the programmer into a rage. This stage is accompanied by an hours-long and profanity-filled diatribe about the limitations of the language directed at whoever will listen. Depression Following the outburst, the programmer becomes aware that hours have gone by unproductively and there is still no solution in sight. The programmer becomes listless. Posture often deteriorates. Acceptance The programmer finally accepts the situation, declares the bug a "feature", and goes to play some Quake.

A black-and-white infographic presents five stages of debugging—Denial, Bargaining/Self-Blame, Anger, Depression, and Acceptance—using simple silhouettes of a programmer at a computer. It humorously parallels the five stages of grief, exaggerating the emotional progression from refusing to believe in a bug to accepting it as a feature and playing Quake. EN: A black-and-white infographic presents five stages of debugging—Denial, Bargaining/Self-Blame, Anger, Depression, and Acceptance—using simple silhouettes of a programmer at a computer. It humorously parallels the five stages of grief, exaggerating the emotional progression from refusing to believe in a bug to accepting it as a feature and playing Quake.

• @profunctor_io / 3039 2019-09-13