4 ms·
I agree this is how it often goes. But this also makes it difficult to give accurate estimates because you sometimes need to prototype 2,3 or even more designs
by devsda 2y ago
I agree this is how it often goes.
But this also makes it difficult to give accurate estimates because you sometimes need to prototype 2,3 or even more designs to workout the
best option.
> writing code should be actually seen as part of the "thinking process".
Unfortunately most of the times leadership dont' see things this way. For them the tough work of thinking ends with architecture or another layer down. Then the engineers are responsible only for translating those designs into software just by typing away with a keyboard.
This leads to mismatch in delivery expectations between leadership and developers.
- lwhi 2y agoIn my opinion, you shouldn't need to prototype all of these options .. but you will need to stress test any points where you have uncertainty. The prototype should provide you with cast iron certainty that the final design can be implemented, to avoid wasting a huge amount of effort.
- marcosdumay 2y agoIf you know so little that you have to make 3 prototypes to understand your problem, do you think designing it by any other process will make it possible make an accurate estimate?