Your question answers itself - if you don't estimate, you don't need to learn how to.
After a while you will just know instantly for some small known tasks how long they will take. That is not an estimate. For bigger unknown tasks, estimation is futile and purely a waste of time
But sadly, the larger industry doesn't work that way. In an ideal world, I'll agree with you. But, having 16+ yrs experience in various types of firms such as enterprise, product and startup industry, providing estimates is fundamental part of building software. If you say, it's not. Then it's an exception the norm. We'll have to agree to disagree on that.
In fact, I went through the comment chain in your posts. Most of what I would have wanted to counter is covered there. But still, you commented in this section, means you want more views for your content 😎🙌 and I'm cool with that.
I tend to agree but usually provide clients with a ballpark range. I explain that the low number is the minimum effort required and the top one is with some nice features like x and x. As for junior devs estimating, I don’t expect them to. I quote the project for how long it would take me and then don’t bill all of the devs hours since they don’t move as fast as I can. As they speed up, I can start increasing their pay for projects.
Simplest and best thing to do is not to estimate. Check out the discussion here: dev.to/carmenhchung/how-to-nail-ti...
If you do not estimate, then how do you learn to estimate?
Your question answers itself - if you don't estimate, you don't need to learn how to.
After a while you will just know instantly for some small known tasks how long they will take. That is not an estimate. For bigger unknown tasks, estimation is futile and purely a waste of time
But sadly, the larger industry doesn't work that way. In an ideal world, I'll agree with you. But, having 16+ yrs experience in various types of firms such as enterprise, product and startup industry, providing estimates is fundamental part of building software. If you say, it's not. Then it's an exception the norm. We'll have to agree to disagree on that.
25 years of experience in similar industries says otherwise, but maybe I just do things differently
Thanks for reading and wish you the best!
In fact, I went through the comment chain in your posts. Most of what I would have wanted to counter is covered there. But still, you commented in this section, means you want more views for your content 😎🙌 and I'm cool with that.
I tend to agree but usually provide clients with a ballpark range. I explain that the low number is the minimum effort required and the top one is with some nice features like x and x. As for junior devs estimating, I don’t expect them to. I quote the project for how long it would take me and then don’t bill all of the devs hours since they don’t move as fast as I can. As they speed up, I can start increasing their pay for projects.
Thanks for reading my article and sharing your thoughts. Cheers!