Monday July 31, 2006
Look Ma! I'm a programmer!
Overheard:
Software Developer 1 (talking about a conversion project): I somehow still understand only 50%. At times I feel like “Got it!” and then it’s like ”...?...”
Software Developer 2: You are a software developer: “getting it” is like Nirvana, the Holy Grail, Enlightenment…
Good thing it’s not bridge-building they were talking about.
But seriously, why are so many projects so poorly engineered? Why is it that understanding other people’s code is like trying to reverse engineer an avalanche?
Filed by Jachin Sheehy under Development
My answer to the first question is time. That is assuming we are not talking about lazy developers, we can never have too much time to do analysis and design and in most cases we don’t. On top of that there is usually the case of scope creep when the project evolves into a monster project in the middle of development.
Thats business and C’est la vie.
As for the second question, there is always a small part in each of us that can’t resist the temptation to leave our mark by writing something so uniquely a product of our own minds. Thereby causing multiple migraines and major hair loss (due to pulling) in our colleagues so privileged as to have the pleasure of maintaining our code.