4 ms·
+1 for the having to maintain your own code. I remember looking back at my own code and swearing "what the *$$# was i thinking.."
by aangjie 15y ago
+1 for the having to maintain your own code. I remember looking back at my own code and swearing "what the *$$# was i thinking.."
- prodigal_erik 15y agoThis is what my boss looks for on résumés. Not loyalty so much as whether you've worked anywhere long enough to have to clean up and rearchitect after your own mistakes, rather than leave an ever-growing trail of (presumably) smoking craters.
- crdoconnor 15y agoI know what I was thinking most of the time: I want to get this thing working and out there as quickly as possible. Deadlines are probably the root cause of most of the world's most horrific hacks. Also, I've never once had a boss turn to me and say "you know what, forget about writing any new features for now - just refactor the code that is working just fine but looks horrible."
- cookiecaper 15y ago>Deadlines are probably the root cause of most of the world's most horrific hacks. I definitely agree with this. I've written some absolutely terrible code in marathon sessions with an impending deadline -- in the worst case, I copy-pasted code in six or seven locations for something that could have and definitely should have been factored out into a function. I just didn't have any time to spare, I had to finish it for a demo in X hours. That whole project was a mess.
- mabid 15y ago100% agreed. Deadlines made me write code that stinks really really bad