Re:Why are developers expected to estimate tasks at all?
by remkop22 on Sunday March 26, 2023 @02:43PM
(#35317926)
As someone who moved from a practical engineering field into software engineering, this separation in tasks between management and developers seems weird. Engineering in general is about finding a local optimum in a multidimensional problem space, one of the axes could be time, another one could be complexity or agility. For me, an engineer is not just tasked with outputting code, but also working out these optimums.
[ Parent
| on HN ]
Re:Why are developers expected to estimate tasks at all?
by rendall on Sunday March 26, 2023 @03:49PM
(#35318776)
Can you expand more? This seems like an important insight to me.
Re:Why are developers expected to estimate tasks at all?
by remkop22 on Sunday March 26, 2023 @04:27PM
(#35319204)
Firstly I think the most important thing in engineering is nothing is free. If you change a parameter in your design something else has got to give. If you increase the cargo capacity of a plane it probably going to going to have a slower cruising speed. The hard part is finding the sweet spot that exactly fits the requirements of the client or use case. And also! now a dosen of other parameters have shifted to, like weight balance or climbing rate. How do these fit in?
Now for software, let's say you have two clients with almost identical requirements for a piece of Software. The only difference being one of them thinks time to market is important, the other one has les focus on time. As a software engineer you should produce two very different pieces of Software for these clients. You will have to make decisions based on the time it will take to implement something and also understand the effects of this on other aspects of the end product.