4 ms·
> I think I'm going quite slowly because I'm having to learn a lot, and I don't think I'll deliver this in 3 days Their first question after you say this will
by BobbyJo 5y ago
> I think I'm going quite slowly because I'm having to learn a lot, and I don't think I'll deliver this in 3 days
Their first question after you say this will be "well, how long will it take?" Whether or not you actually have any idea how much time you'll need, you'll have to give an answer, and on that blows the schedule up too much will be strongly frowned upon.
Now you've realized you're working for a crappy PM/EM who wants you to do their job for them, since they should have already known that the estimate from the first engineer will be nowhere close to the reality from the second.
The best managers I've had have been the ones that rarely need time estimates. They know enough about what's going on, and the comparative skill levels of the engineers, to give reasonable estimates themselves in most cases.
- ebiester 5y agoThat is a function of time in company and continuity of team more than skill of manager.
- BobbyJo 5y agoI disagree. I think skill of manager plays into it more than anything. I've seen managers come on board and within 3-6 months were able to operate like this. They focused on learning the technology and getting to know the people before they started actively managing. These were large, long running teams they were joining too.
- mcspiff 5y agoYup, definitely agree with this. I’ve noticed these are the managers that “feel like they’ve always been there”.
- pojzon 5y agoI can double tap on that. Good manager is able to understand the product and estimate by himself. Ive had quite a bit of experience working with different managers and overall those who were „invested” and got familiar with the product „really well” could estimate for the team.