{"id":139,"date":"2001-12-06T16:53:00","date_gmt":"2001-12-06T22:53:00","guid":{"rendered":"http:\/\/www.lordandrei.com\/blog\/?p=139"},"modified":"2001-12-06T16:53:00","modified_gmt":"2001-12-06T22:53:00","slug":"why-i-want-a-heisenberg-compensator","status":"publish","type":"post","link":"http:\/\/www.lordandrei.com\/blog\/2001\/12\/06\/why-i-want-a-heisenberg-compensator\/","title":{"rendered":"Why I want a Heisenberg compensator!"},"content":{"rendered":"

Let me rant a moment about the accursed “Heisenbug<\/b>”<\/p>\n

For those who haven’t come in contact with Friar Heisenberg, the uncertainty prinicipal is well described here.<\/a><\/p>\n

So what does this have to do with a software developer in the Mac world?<\/p>\n

In the world of development you write a complex program. It does lots of little, mini activities to accomplish a greater whole. Typically a good program writes a completely error free program on the first attempt. Yeah…right<\/i> So, okay. we make mistakes and the program is fraught with bugs. However<\/b>, we have a tool to let us find the bugs. It’s called “Debug Mode.” With this powerful tool the program does all it’s little machinations and also tells the programmer what it’s doing.<\/p>\n

Well, tonight I got a heisenbug. I built the program and the f*-er exploded. <tone VOICE=Akroid FILM=Ghostbusters>Real nasty one!<\/tone>
\nAt the time I didn’t know it was a heisenbug. I figured….”Debug mode” that’s how to do find the problem.
\nBut no!<\/font><\/b> This was a heisenbug. And by looking…I changed its environment. I invoke my debug tool and the error goes away.
\nDamn, Zut, Merde, Gad Verdamma….F***<\/p>\n

So now, I want a “Star Trek” Heisenberg Compensator to point at my code when I’m debugging.<\/p>\n

And just to tell some of you how I feel<\/p>\n

<tone VOICE=me type=regression>i want a po<\/b>ny.<\/tone><\/p>\n

Share this:<\/h3>