Re:Why are developers expected to estimate tasks at all?
by dclusin on Sunday March 26, 2023 @03:40PM
(#35318681)
Assuming you’re pretty close to the hardware? As a standard backend web service dev os/library/device bugs are incredibly unlikely and usually defective application software is to blame. Not saying it doesn’t happen, but I can’t recall in recent memory this sort of thing happening as high up in the stack I work.
Re:Why are developers expected to estimate tasks at all?
by AlotOfReading on Sunday March 26, 2023 @08:40PM
(#35321438)
That's just the sort of stuff I see, but long tail issues that take weeks or months to diagnose can happen anywhere in the stack. Sometimes it's a hardware issue, sometimes it's a compiler bug, sometimes a VM bug, a missing browser feature, etc. Any of that can crop up even with "trivial" changes. I'd argue that it's not useful to include that in your estimates, but they're nevertheless possible and need to be incorporated in scheduling.
Re:Why are developers expected to estimate tasks at all?
by antipotoad on Sunday March 26, 2023 @03:48PM
(#35318765)
May I ask how you identified them as silicon bugs? And by silicon bugs do you mean random bit flips, or something else?
Re:Why are developers expected to estimate tasks at all?
by AlotOfReading on Sunday March 26, 2023 @08:37PM
(#35321412)
I probably should have said hardware bugs, as only one is in an IC (specifically an IP block). The rest are things like improper layout, faulty components, wrong value passives, etc.
For context, my team is in exactly this situation with several silicon bugs we found last month.