All programmers are optimists
by Grant McNeil · in Technical Issues · 07/08/2002 (4:52 pm) · 6 replies
"All programmers are optimists. Perhaps this modern sorcery especially attracts those who
believe in happy endings and fairy god-mothers.
Perhaps the hundreds of nitty frustrations
drive away all but those who habitually focus on the end goal.
Perhaps it is merely that computers are young, programmers are younger, and the young are
always optimists. But however the selection process works, the result is indisputable:
'This time it will surely run,'
or
'I just found the last bug.'."
-- Fred Brooks, The Mythical Man-Month
(submetted to the forum by Grant McNeil)
believe in happy endings and fairy god-mothers.
Perhaps the hundreds of nitty frustrations
drive away all but those who habitually focus on the end goal.
Perhaps it is merely that computers are young, programmers are younger, and the young are
always optimists. But however the selection process works, the result is indisputable:
'This time it will surely run,'
or
'I just found the last bug.'."
-- Fred Brooks, The Mythical Man-Month
(submetted to the forum by Grant McNeil)
About the author
#2
Optimistic my a*se ;) The cup is officially half empty...
07/09/2002 (3:16 am)
No I didn't have time, but then again with this spiraling work load, endless bugs, users that have less than a clue and continually alter the spec... but whats the point, by the time i'm finished they'll be working on the next version...Optimistic my a*se ;) The cup is officially half empty...
#3
Murphy was an optimist.
When a programmer gives you an estimate of time to complete a particular task take that number double it and move up to the next unit of measure, i.e. 2 hrs = 4 days; 1 day = 2 weeks, etc.
12/23/2002 (2:18 pm)
Two things I've learned after 19 years in this industry:Murphy was an optimist.
When a programmer gives you an estimate of time to complete a particular task take that number double it and move up to the next unit of measure, i.e. 2 hrs = 4 days; 1 day = 2 weeks, etc.
#4
12/23/2002 (8:44 pm)
The reason is programmers can see the function for the code. They are so concerned with HOW to do something, or that they already "know" how to do something, that they never really address the "what" and "why" something needs to be done. 9 out of 10 times if you really address the "why" and "what" correctly, you will decide NOT to do the coding you thought you "knew" how to do.
#5
A programmer will know how to solve the problem with code. A great programmer will know when not to solve the problem with code.
12/24/2002 (8:51 am)
Jarrod, my sentiments exactly.A programmer will know how to solve the problem with code. A great programmer will know when not to solve the problem with code.
#6
12/24/2002 (11:12 am)
Based on that criteria, then I must be a great programmer. I've 'chosen' (not failed mind you, but chosen) not to solve a lot of problems :) 
Torque Owner DavidRM
-David