3 ms·
Most engineers can guestimate, but I do know one that would say the following: no idea, I will have to do two days of research on the matter and come back to y
by bryanrasmussen 4y ago
Most engineers can guestimate, but I do know one that would say the following:
no idea, I will have to do two days of research on the matter and come back to you with an estimate in standup the day after tomorrow. (really, he said exactly that one time, it was a wonderful expression of his character I thought)
The person who just says no idea, and doesn't have a way to get to an idea, seems to have a very problematic limitation.
- wildrhythms 4y agoI don't agree with this. If an engineer can't estimate how long something will take, usually that's an indication that your requirements are unclear, or there's a history of changing up requirements on people. What you've labeled as a limitation is probably an engineer being honest with you.
- bryanrasmussen 4y agook so in this case I would probably expect them to say: the requirements are unclear - that right there is them having an idea how they are going to be able to give you an estimate, by forcing you to be clear in your requirements. That would actually be an engineer being honest. or there is a history of changing up requirements on issues like this, I can give you the estimate of what it will be with the current requirements but if the requirements change, as in my experience they are likely to, then that estimate will have to change as well. - this would also be an engineer being honest. Both of those honest examples aside if the engineer replies no I can't make an estimate and I never will be able to it is probably the engineer being a bit pissy. And I know definitely one or two guys who would exactly behave in this manner. unless you are dealing with the first time implementation of something that there is only mathematical theory backing it and no previous implementations in the world, I have a hard time seeing how you can construct a situation in which an engineer cannot come with an estimate AND cannot find a way to figure out what they need to come with an estimate (more specific requirements, research on the matter). If they can't figure out at least one of those things I'm going to think it is probably a limitation on the part of that engineer. Finally, I am an engineer. Although I tend to be one of those arrogant guestimaters, which is a failing in my personality.
- anarazel 4y agoIt's not uncommon IME that doing the work to come up with a reasonable estimate is 80% of the final work. E.g., addressing a scalability issue might require a bunch of profiling work, then a bunch of experimentation / thinking about developing a lock free algorithm. Or it might turn out that reducing false sharing a bit will give large enough benefit on its own. Without having done most of that I won't know whether it's a few days or many weeks.
- bryanrasmussen 4y ago>E.g., addressing a scalability issue might require a bunch of profiling work, then a bunch of experimentation / thinking about developing a lock free algorithm. Or it might turn out that reducing false sharing a bit will give large enough benefit on its own. so this sounds like my example of my friend that I gave above who would say I will have to do a bunch of profiling work first and then a few days of investigation before I tell you how much it is actually going to take. I don't say you can't run into uncertainties and be unable to estimate until you have clarified those uncertainties, I also don't say that you can't run into uncertainties in the actual implementation and have your estimate be woefully off, not every estimate needs to be correct.
- marcosdumay 4y ago> It's not uncommon IME that doing the work to come up with a reasonable estimate is 80% of the final work. That estimate you do after finishing 80% of the work is probably orders of magnitude smaller than the real thing. More realistically, if you don't have the experience for an estimate beforehand, you also don't have the experience to know when you covered enough of the high-risk subproblems, so you have no basis at all to decide how complete your research is. You will only have a reasonably safe estimate by the time you finish the task.
- anarazel 4y agoThere's tasks where experience doesn't tell you ahead of time how long something takes. If you need to figure out a [novel take on an] algorithm, it'll be hard to predict the time even if you did things like that plenty times before. And you'll be able to judge the remaining work after pretty decently.