Wednesday, March 02, 2005

hints

You're fixing bugs in a language that was only academically interesting (also you still can't think of a commercial-grade product written in it)

The bug reports make no sense to you. You have never used the application before, so this aspect makes sense to you). On further investigation, it doesn't make sense to (a) the person who submitted it (b) the people who reviewed it (c) the people who distilled the essence of it in the notes.

You know what needs to be done to fix a bug, but at a macroscopic level. Even managerial presentations have less fluff than this. You stare at the code for long moments of time. The syntax makes sense. The IDE causes programs around it to tank. Navigability is an attribute the code never intended to boast. Modularity and separation of concerns are distant dreams. Utopia, even.

You refresh your slashdot tab and the newest article bears the title When Should You Quit Your Job?.

The most successful comedians had extremely unfunny private lives. You could take consolation in that except that you can't even fake happiness.

No comments:

 
Creative Commons License
This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License.