Code Zombie
Apr. 20th, 2006 12:54 amThere is a reason why all the best (/my best) code is written between the hours of midnight and 4am.
The reason is because if I'm working late, I become not "Supercoder", as I previously thought, running on pure caffeine, sleep dep and hatred of the Foul Code Beast, but instead a far more malign being: Code Zombie.
Code Zombie does not question. Code Zombie does not even think. Code Zombie simply codes.
But, importantly, Code Zombie does not shirk or over-analyse.
And this, it seems, is why I actually get the job done.
I don't try to find the clever, elegant solution. If I look at something and realise "Oh! I wrote this all ass-backwards!", instead of rewriting thousands of lines prettily and sensibly, I think "Yeah, but if I continue to think that way round, there's a one-liner that fixes all those bugs. Neat. Done. Next."
My business partner seems to write almost exclusively as Code Zombie, which means he is better at hitting his deadlines without breaking a sweat, but only if there's not some radical rethink-requiring problem. He ignores the tedium of some of the bigger tasks, he doesn't 'waste' time that I would spend trying to make things modular and Klev0r, he just ploughs on with it.
Which is one reason I wince when I have to read his code, but it does, to be fair, get the job done.
I have a horribly ingrown need to make stuff legible and maintainable, which is often inappropriate for single-person, 1-3 month projects. The trade off for the Pretty Codings isn't worth the time I'd save if I was Teh Hackmeister. My mild-mannered alter-ego that operates in daylight hours tries to write Good Code. Often to little benefit.
Still, I do avert a few big and nasty problems through dilligent planning, so it's not all bad.
I'm sure there's some magical Xtreme Programming solution other than this Jeckle-and-Hyde approach, but tonight I'm just happy that I've solved the next day's problems (to be fair, by working the next day's hours) tonight, and as such can have a drink and chill out and probably not be that efficient tomorrow, but at least do so in the knowledge that I'm ahead of schedule.
Fucking Nora. Whattaday.
The reason is because if I'm working late, I become not "Supercoder", as I previously thought, running on pure caffeine, sleep dep and hatred of the Foul Code Beast, but instead a far more malign being: Code Zombie.
Code Zombie does not question. Code Zombie does not even think. Code Zombie simply codes.
But, importantly, Code Zombie does not shirk or over-analyse.
And this, it seems, is why I actually get the job done.
I don't try to find the clever, elegant solution. If I look at something and realise "Oh! I wrote this all ass-backwards!", instead of rewriting thousands of lines prettily and sensibly, I think "Yeah, but if I continue to think that way round, there's a one-liner that fixes all those bugs. Neat. Done. Next."
My business partner seems to write almost exclusively as Code Zombie, which means he is better at hitting his deadlines without breaking a sweat, but only if there's not some radical rethink-requiring problem. He ignores the tedium of some of the bigger tasks, he doesn't 'waste' time that I would spend trying to make things modular and Klev0r, he just ploughs on with it.
Which is one reason I wince when I have to read his code, but it does, to be fair, get the job done.
I have a horribly ingrown need to make stuff legible and maintainable, which is often inappropriate for single-person, 1-3 month projects. The trade off for the Pretty Codings isn't worth the time I'd save if I was Teh Hackmeister. My mild-mannered alter-ego that operates in daylight hours tries to write Good Code. Often to little benefit.
Still, I do avert a few big and nasty problems through dilligent planning, so it's not all bad.
I'm sure there's some magical Xtreme Programming solution other than this Jeckle-and-Hyde approach, but tonight I'm just happy that I've solved the next day's problems (to be fair, by working the next day's hours) tonight, and as such can have a drink and chill out and probably not be that efficient tomorrow, but at least do so in the knowledge that I'm ahead of schedule.
Fucking Nora. Whattaday.