4 ms·
> Anyone who's worked in tach a while has seen cases where a dev has just flat out refused to do something a manager has asked them to do. Why? Ego is the only
by lkbm 6y ago
> Anyone who's worked in tach a while has seen cases where a dev has just flat out refused to do something a manager has asked them to do. Why? Ego is the only reason when you get paid either way.
I don't think I've seen that yet, but if it came up with any of my coworkers, it would be because of ethical concerns. "Hide the cancel button", "Remove the unsubscribe link", etc.
Are you talking about people saying things like "I'm a senior engineer. Get the newbie to do that task"? I can't imagine that flying for a second where I work. You can try making the case that it's a poor use of your time, but flat-out refusing to do something out of ego would be the reddest of red flags.
(fwiw, I'm in Austin, not SV.)
- question000 6y agoYeah I've seen situations where basically a dev wants to take project in a direction and the manager repeatedly shoots it down until they quit or are fired. They will just argue that the manager is micro-managing and making technical decisions, but in reality it's just matter of how the business must operate and the dev is actually stepping on the managers toes. Devs will also just argue that doing some UI related changes are pointless even though managers have requested them repeatedly and clearly prioritize them. I've seen all forms of recalcitrance.
- phreack 6y agoMaybe it was an unrealistic task, like 'we've agreed to have this <10 month thing> built in 2, so get to it'. If agreeing to such a thing means it becomes your fault when it inevitably fails, it's necessary to refuse and reschedule. Or not, but I can imagine many exceptions besides ego that would be reasonable. If it's just a Rockstar tantrum, then you're better off firing that dev asap and I can't even imagine such a person getting away with it, though I've never worked in SV.