34

Every year, my company organizes an internal seminar week for its engineers and developers. I helped plan it this year and, since I also ran a few sessions, was absolutely exhausted by the end of the week.

On Friday of that conference week (after I'd spent four hours in our engineering building), I come back to my desk to discover that a coworker managed to, single handedly, get our boss to agree to shortening our release cycle to one that, without dramatic infrastructure changes, would require about 8x the developer overhead than today's. ...The test cycle I am supposed to pick up in a month.

When asked about it, he said he was so full of energy, why wait for automaton? What better way to inspire us to improve than to switch right now? The worst that can happen is just a few bugs.

I love my job, but I can't stand this guy. 😒

Comments
  • 3
    Wow, your coworker seems not to be the brightest lamp in the lamp shop...

    "just a few bugs"... TRIGGERED
  • 4
    Wait what!?

    Draw it out as a pretty picture for the manager... your co-worker can be a frustrated womble in the diagram, the manager can be crying in a corner and you can be cleaning up the pieces of their tattered dreams.

    What was the exact change?
  • 2
    @jmacmi2 I was gone for his initial pitch to the rest of the team. He got them on board before making it public and then let me know.

    There aren't any broken pieces to pick up yet, so I'm afraid that might not work so well. I have responded in writing to his official proposal, but his response failed to address my concerns with overhead.
  • 3
    @starless dammit, good luck with the good fight.

    Hopefully it doesn't cause you too much trouble.
Add Comment