Re:Designer Eats Engineer
by ChuckMcM on Sunday January 13, 2013 @10:40PM
(#5053169)
I certainly resonate with this line of reasoning. When working for Intel (putatively as a hardware engineer) I got criticized during a review period for 'sandbagging'[1] with the justification that the assembler I wrote I said would take 3 months (which it did) but I spend two months goofing off and one month writing it. I realized two things, one that hardware engineering had lots of great milestones, and two that software development sounded a lot like 'art' to people who aren't familiar with it.
The salient clue was the Michelangelo quote "Every block of stone has a statue inside it and it is the task of the sculptor to discover it." Where a programmer might say every megabyte of memory has a program inside it and is is the task of the programmer to discover it. There aren't as many really crisp milestones you can say "we are here" and point to the place on the schedule where you are 'n' weeks away from completion.
[1] sandbagging - creating an estimate for the time it will take to do something far in excess of the time it will really take in order to facilitate goofing off while not getting behind in your schedule commitments.
The salient clue was the Michelangelo quote "Every block of stone has a statue inside it and it is the task of the sculptor to discover it." Where a programmer might say every megabyte of memory has a program inside it and is is the task of the programmer to discover it. There aren't as many really crisp milestones you can say "we are here" and point to the place on the schedule where you are 'n' weeks away from completion.
[1] sandbagging - creating an estimate for the time it will take to do something far in excess of the time it will really take in order to facilitate goofing off while not getting behind in your schedule commitments.