June 3, 2005 12:44 pm

If you ever spend all day programming, and at the end you come to a stopping point where you think you’ve got the main features implemented and the glaring bugs worked out, and now you’d like to have somebody play with the software to see what comes up, then consider this:

Wait until tomorrow.

Wait until tomorrow morning when you can fire up your software and use it for ten seconds, because that’s when you’ll realize that somehow, without you realizing it, it crashes on launch every time. That’s when you’ll notice that the major new feature you thought was done and working actually introduces another bug so heinous as to make the program unusable – and untestable.

Last night you were so blasted out of your mind from looking at code all day long and trying to squish bugs and figuring out how to do that thing you don’t know how to do by reading the accursedly obtuse documentation, you couldn’t see these things which would normally catch you immediately, and will catch your testers, because they’re going to be bitching at you since your software didn’t even launch. All I’m saying is wait until tomorrow. A shower and a good night’s sleep will allow you to see with the clarity you need to not make people hate you.

With that in mind, if you have a Mac and you want in on the action, hit it with the latest build.

4 Responses to “Quantity is Job One”

indorphin says:
June 3rd, 2005 at 1:34 pm

It’s the hotness.

indorphin says:
June 3rd, 2005 at 4:29 pm

keeps hanging. Cursed beta releases.

Allie says:
June 8th, 2005 at 9:47 pm

You should really update with something I can understand. :) I mean I tried to read the whole thing, but I think I need to be really into computer programming to understand, maybe i’m losing my geekiness…

indorphin says:
June 9th, 2005 at 1:17 am

I’m not into programming at all. Never wrote a program in my life. I’m just a beta tester. And alpha tester.

Well, for iTC anyway.