Ever realize that you are sooo deep into a project and you don't have time for a seriously eloquent solution? Ever, then, come to the conclusion that you need to "just get it done" (otherwise known as the "JGID" methodology), and write up some hacky solution that works, but you *know* in your heart is some of the ugliest code in the history of mankind? You write code that you *know* is so bad that you put in a comment acknowledging the hack and de facto apologizing for it in the hopes on code review you'll get at least some consideration to recognizing your hack? You end up actually going so far as to put it on the development schedule to go back and refactor the mess you made...creating a "shiny mess", knowing that so long it works you'd rather be shot than have to touch it?
I bet none of you has, but I darn sure know I did today.
I feel so dirty....
I just hope the code gods forgive my transgression.....forgive me for I have hacked....
I think I'll go home and read three chapters of "Object Thinking" to try and wash this code guilt off me...
Edit: I am unable to successfully comment on my own blog at the moment, but I did have a reply for Carl (see below)
Yeah, I know, right? Imagine a bad coder like me (how you know me so well, I'll never figure out) actually *going* home! I should probably spend more time at work. If I would be willing to give up my life for my employer (as I have in the past), why, I'd have lots of time. Good idea, Carl. :-) Instead, though, I think I'll plan on the 9.5 hours a day I give them and do what I can in the time they give me. Probably makes me a bad employee, but hey, my family likes it. :-)
posted @ Thursday, July 31, 2008 12:11 PM