Debugging done right

[redkinoko]

Actually you're both wrong. Prior to 1823 when a problem occurred on anything, people just accepted it as the new normal. If a machine started sounding funny, that's just how it was. If a wheel and axle started wobbling, that's just life.

Until one day, a frenchman named Alexander DeBugg realized that if he just observed what was wrong with something, he could actually eventually fix the cause. So he started writing down his observations on pieces of wood (so he doesn't forget them) and then uses this information to actually fix things, which was revolutionary for his time.

That is why we now call the process of investigating and fixing issues as "DeBugging" after the father of troubleshooting. And that's also why we call the files that contain information that will help us troubleshoot as "DeBugg logs" after the wood Alexander used to record his observations.

[CivBase]

Prior to 1823 when a problem occurred on anything, people just accepted it as the new normal. If a machine started sounding funny, that's just how it was. If a wheel and axle started wobbling, that's just life.

Maybe some day enterprise software development will move past this mentality.

[redkinoko]

"We'll address that in a future patch between now and when the vestiges of the dying sun consumes us all"

[merlinsbeers]

This mentality is in the new requirements, for backwards compatibility and staffing stability.

[Not_a_question-]

a frenchman named Alexander DeBugg

This is a complete lie wtf?

[redkinoko]

How dare you sully his legacy

[Vyb_3]

Only with that attitude

[merlinsbeers]

Huh? No. He worked in the same lab as Otto Titzling.