My boss has recently called me out on a problem I've developed in recent weeks. I have an affinity for elegant, tight, well-refined code. The problem is, to achieve that result, one often spends FAR too long in the engineering stage. Sometimes quick and dirty code really is the best approach, even if it's ugly as sin and makes other devs wince when they see it.
Sure, there are things that I will still avoid like the plague, and there are things that I will continue to do even though they aren't technically necessary. I won't put all my code in the global scope and let it run in crazy freestyle spaghetti form. I will make sure that anything appearing more than twice gets the distinction of being in its own function. But there are a few projects on my plate that really shouldn't take more than an hour or two to see completion status, and for some ridiculous reason, I find myself spending a couple days on them.
I know it frustrates the hell out of people, especially when they're used to seeing me "just get shit done."
So, again, a personal goal: know when to worry about elegance, and when to pump out the code like your fingers have teh diarrhea.
No comments:
Post a Comment