stbenge wrote:
> On 1/31/2011 1:38 PM, Darren New wrote:
>> stbenge wrote:
>>> Sometimes it seems like the problems expand outward in a branching
>>> structure...
>>
>> I have coined the term Zeno's Debugger for that.
>>
>> Every time you try to figure out what's causing the error, you have to
>> first debug the tool you're using to figure out what's causing that
>> error, recursively.
> 
> But what do you call it when the only thing stopping your software's 
> deployment is one tiny exe that happens to be bundled into one humongous 
> development kit?

So you go to download the kit and you need to make up an account to download 
it. But the make-up-the-account doesn't work through the corporate firewall, 
so you go home. But your home computer has firefox and the download doesn't 
work with that. So you install Chrome and manage to sign up, but they don't 
take gmail addresses for logins. So you go to log in over the VPN, but the 
VPN software has been upgraded, so you need to take your VPN box back to 
work anyway to get reflashed. So you go back to work to download the file 
but it doesn't come through the proxy. So you bypass the proxy but there 
isn't enough temp space to download the package. So you go to back up some 
useful files but the USB drive has gone missing. So you ask around to see 
who has the USB drive .....

When, really, all you wanted was to write a f'ing piece of code.

-- 
Darren New, San Diego CA, USA (PST)
  "How did he die?"   "He got shot in the hand."
     "That was fatal?"
          "He was holding a live grenade at the time."

Post a reply to this message