2 ms·
Sorry yeah, I communicated that poorly. "big penalties" is meant to mean exactly what you wrote. Spend some time studying why they went over and do a write-up o
by bane 12y ago
Sorry yeah, I communicated that poorly. "big penalties" is meant to mean exactly what you wrote. Spend some time studying why they went over and do a write-up on it.
I've found most developers hate documentation more than anything, and making them do work like this is a "big penalty".
I agree that software estimation is hard, but that's usually at the macro-level. Micro-level estimation, within a few percent is usually pretty reliable. What happens at the macro level is that those tiny percent uncertainties compound up and interact in all sorts of horrible ways.
But "do you think you can build the database connector and load the data by next Friday?" is not too hard of a problem, even at the junior level.
I think more importantly, if they come back and it's not done, but it's not their fault, they'll get comfortable coming to give you bad news, which is super-critical for macro-planning.