codeinabox@programming.dev to Programming@programming.devEnglish · 1 day agoHow I estimate work as a staff software engineerwww.seangoedecke.comexternal-linkmessage-square18fedilinkarrow-up169arrow-down15cross-posted to: lobsters
arrow-up164arrow-down1external-linkHow I estimate work as a staff software engineerwww.seangoedecke.comcodeinabox@programming.dev to Programming@programming.devEnglish · 1 day agomessage-square18fedilinkcross-posted to: lobsters
minus-squareidriss@lemmy.mllinkfedilinkarrow-up11·17 hours agobruh, so it’s not me who was stupid all this time for not being able to put an estimate for large initiatives. It always feels forced to give an estimate.
minus-squarecalliope@retrolemmy.comlinkfedilinkarrow-up7·12 hours agoDefinitely not just you! This author is 100% right. One of the main jobs of a software developer is continually trying to convince people estimates are kind of stupid. If we already knew exactly how to build something, we would have built it already. The whole point is that it doesn’t exist, and there are a lot of inherent risks when building something that doesn’t already exist! Like, duh. The issue, of course, is that everyone not in software thinks it’s like traditional manufacturing and not research and development.
bruh, so it’s not me who was stupid all this time for not being able to put an estimate for large initiatives. It always feels forced to give an estimate.
Definitely not just you! This author is 100% right.
One of the main jobs of a software developer is continually trying to convince people estimates are kind of stupid.
If we already knew exactly how to build something, we would have built it already.
The whole point is that it doesn’t exist, and there are a lot of inherent risks when building something that doesn’t already exist! Like, duh.
The issue, of course, is that everyone not in software thinks it’s like traditional manufacturing and not research and development.