1) Thinking you might make out with someone later can get you through a day full of crappy java code, but then when it doesnt happen, again, well your life sucks all that much more, especially if you no longer have a motorcycle to burn off all the energy with. Not that the highways here are that great anyway--too many places for cops to hide. I might try to look into some kind of gas grenade for evasion, but at those speeds I would have to launch it in front of me and ride through it. Thats a lot of gear anyway.
2) Programmers who completely rewrite a bunch of data classes, and who leave the old set because it can't be removed, should write the damn converter when they write the new ones. That way, people like me won't be stuck trying to make sense of the mess later.
3) Code should be written to die honorably. Code should not be written to live forever like they teach you in programming class. Code that is designed well can be easily replaced, taken out back, and shot. Code that is not designed well lives on because it is an undead zombie and you can't take it out without the coding equivalent of a double barreled shotgun, which requires destroying (i.e. rewriting) a lot of otherwise-innocent code in the process.
Also, FYI, this isn't really for any of you; I just wanted to clear some space on my whiteboard for this unnecessarily complex class diagram. Seriously--we have 3 data types, but I'm already at 8 different java classes and still counting....
No comments:
Post a Comment