Soft Skills Engineering · Hands-On Engineering Podcasts · November 2026
Jamison had suggested timing a task as if it had to be done in a week, a day or an hour. Dave adds that a junior developer should ask the manager what size the task is meant to be, the way a product manager asks for an estimate.
Great idea.
…to do it in a day? What if I had to do it in an hour? What if I had to do it in 10 minutes? Just see how hard you can push it. You might not use all those. They might not throw some of them away, but I think it's useful to challenge your assumptions about how long something might take sometimes.
I think that's great. And can I take that in a slightly different direction? Talk to your manager who's giving you, whoever it is is giving you your task assignments and ask them, what size do you want this to be? You know, like, or what size would you expect an engineer to do this in to help understand? Because this is kind of like buying and selling stuff. And I've noticed product managers, like good product managers, do this really well. They'll ask an engineering team, hey, what's the effort to build this feature? And a good engineering team will tell them, like, oh, yeah, that's like a one-week kind of project. Oh, that's like an afternoon kind of project. Well, that's like a month of work. And the product manager will decide if he or she wants the feature at that price. You know, like, oh, this is a three-month project. Don't want it. And sometimes they'll ask, what's the one-week version of this? Because that's all I could afford. And then the engineers describe it and the product manager goes, I don't want it, or I do want it. And I think you, as a junior engineer, are one of the downside…
Also, the robots do that to you. They say, and this will take three weeks. And then you say, no, do it. And then
it's done. You go do it. Sloppy and paste.
Okay. Have we answered? Yes.