News for hackers. Stuff that matters.
Re:Coding, Fast and Slow: Developers and the Psychology of O... by DougWebb on Tuesday April 23, 2013 @07:40PM (#5598683)
How do you come up with the range?

How do you know how much risk you're taking on that the upper end of your range is not seriously under estimated?

Re:Coding, Fast and Slow: Developers and the Psychology of O... by k-mcgrady on Tuesday April 23, 2013 @08:16PM (#5598818)
I've just learnt through experience. There is obviously still some risk involved but it's reduced. When I'm working on projects that are similar to ones I've worked on before I use a smaller price range and if I'm working on something totally new to me I will use a larger price range to keep the risk as minimal as I can.
Re:Coding, Fast and Slow: Developers and the Psychology of O... by kybernetikos on Wednesday April 24, 2013 @03:43AM (#5600339)
That's an interesting approach, but in fact your range is a time estimate, so it's not quite true that you've stopped doing time estimates, it's just you've stopped telling the cusetomer exactly what they are.