3 ms·
I've always thought the opposite, which is estimation is fuzzier than design. I mean, who here hasn't been off on an estimate in the last month or so? Develop
by bigsassy 17y ago
I've always thought the opposite, which is estimation is fuzzier than design. I mean, who here hasn't been off on an estimate in the last month or so? Developers are notorious for making bad estimates. See http://www.codinghorror.com/blog/archives/001284.html http://www.codinghorror.com/blog/archives/001284.html.
- mattyb 17y agoURLs automatically become links, no need for tags.
- bigsassy 17y agoAh, thanks for the tip.
- tptacek 17y agoYou could let a candidate be fuzzy with estimation, but it's much better to dig in. If they say something will take 40 hours, ask why. The "why" answers are going to tell you a lot about how they design, code, and test, and those answers are going to come under pressure (you want the smallest reasonable time, and they know it, but you also want to detect BS). Also, I think design skills are less valuable than estimation skills. If you can estimate reliably, you can design. The reverse isn't true.
- dfranke 17y agoEveryone is notorious for making bad estimates. It's just that developers make estimates more often than most other professions do. http://lesswrong.com/lw/jg/planning_fallacy/ http://lesswrong.com/lw/jg/planning_fallacy/