Are 10% of developer really "ghost engineers" who pretend to work? Are engineers in big tech just lazy? Do Stanford MBAs just need to be stopped?*Chapters*0:...
We recently got moved under someone who leads call center operations and they’re wanting to apply similar metrics to the devs to “ensure they’re being productive the entire time”. I told them that there’s lots of work they do outside the normal 9-5 and that you can’t just measure what someone does by lines of code created else you’ll end up with a 30 line if statement instead of a for each letter loop, but they don’t seem to care. If things get implemented I’m just waiting for the shit show it’ll cause.
Yup. I judge devs by problems solved (bugs fixed, features implemented) based on initial estimate and actual delivery time. If they’re consistently off, they either need help with estimation (I’ll tell them to increase estimates) or they aren’t doing their job. I don’t care if the solution is 1 lines or 1000 lines (well, I prefer less code), I care if they feel confident in their estimate before starting work, and if they’re able to deliver close to their estimate. I also care what others on the team think about their estimate, and I’ll review anything that seems out of whack.
And this is why I refuse to work anywhere where the people managing devs don’t have dev experience. My boss was a dev, and they’re fantastic at catching me on my BS, which tells me I’m being fairly evaluated. I can’t ask for more than that.
We recently got moved under someone who leads call center operations and they’re wanting to apply similar metrics to the devs to “ensure they’re being productive the entire time”. I told them that there’s lots of work they do outside the normal 9-5 and that you can’t just measure what someone does by lines of code created else you’ll end up with a 30 line if statement instead of a for each letter loop, but they don’t seem to care. If things get implemented I’m just waiting for the shit show it’ll cause.
Yup. I judge devs by problems solved (bugs fixed, features implemented) based on initial estimate and actual delivery time. If they’re consistently off, they either need help with estimation (I’ll tell them to increase estimates) or they aren’t doing their job. I don’t care if the solution is 1 lines or 1000 lines (well, I prefer less code), I care if they feel confident in their estimate before starting work, and if they’re able to deliver close to their estimate. I also care what others on the team think about their estimate, and I’ll review anything that seems out of whack.
And this is why I refuse to work anywhere where the people managing devs don’t have dev experience. My boss was a dev, and they’re fantastic at catching me on my BS, which tells me I’m being fairly evaluated. I can’t ask for more than that.