| > engineer arrogance And this is the twilight-zone reality that software developers are forever stuck in: Manager: "I need you to integrate the TPS reports with JIRA for a client" Developer: "Ok, I can look into that" Manager: "How long is that going to take? Put some story points on the JIRA task." Developer: "Well, I've never done that before, so I'll have to do some research and I can't really say for sure-" Manager: "I need you to say for sure. Knock it off with your engineer arrogance and suck it up and help your colleagues. I'm so sorry that I pulled you out of your 'deep flow' state but we're trying to reach our goals here" Developer: (heavy sigh) "Well, a week maybe? If I can focus on just this and not all the other things I'm currently tasked with-" Manager: "No, subtask it out to individual tasks of no more than four hours each. And you'll need to spend an hour every day in a status meeting so you can spend five minutes updating the status of your subtasks and listening to everybody else's unrelated statuses". |
But if I had a work environment like this, I would be blaming management, and not Jira.
And I should have been clear: not many engineers are actually "how dare you interrupt me, I'm an ENGINEER" types, in my experience.
But I guess I've seen enough blog posts that are so precious about being a software engineer, and so (perhaps unintentionally) dismissive of other people in the org who are also trying to do their jobs, that I probably got triggered a little.