If you routinely “get heated” at work, the best-case scenario is that you’re part of a tight-knit team of confident people who aren’t put off by it. No harm, no foul. But the second someone comes onto your team who’s not so confident, or you have to communicate outside of your team, it becomes a big problem. It’s a bad way to treat your colleagues — even undirected or casual anger intimidates and alienates the people around you — and it makes you a less effective engineer.

all 19 comments

sorted by: hot top controversial new old
[–] 58 points 2 weeks ago

Nah, it’s okay to be angry. It’s not okay to express that anger as hostility.

  • source
  • [–] 24 points 2 weeks ago

    This is valid not only for engineers. Possibly for all work situations.
    A lesson I too had to learn the hard way.

    OTOH expressing anger in your life must be possible. Maybe it's possible to do that constructively.

  • source
  • [–] 19 points 2 weeks ago

    I don't regret the times I show anger at work, but it's a definitely a fine line that can leave me feeling a bit uneasy afterwards. It's one of the "social capital" things; you need to earn enough good will to spend your anger on the battles that really matter to you.

  • source
  • [–] 15 points 2 weeks ago (1 child)

    I used to care more about work. But this job pays garbage and is frothing over AI, so fuck them.

  • source
  • hideshow 2 child comments
  • [–] 13 points 2 weeks ago (1 child)

    Hating on Jira and Confluence together is a great team bonding experience.

  • source
  • hideshow 2 child comments
  • [–] 4 points 2 weeks ago (1 child)

    Why is the start stand up button in a hidden menu while complete sprint not? One you do daily, the other once a sprint.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 8 points 2 weeks ago

    tell this to my fucking manager LMAO

  • source
  • [–] 6 points 2 weeks ago (1 child)

    When I get genuinely frustrated and irritated, when I communicate that it's typically still with a smile. Dark humor, if you will. I'm mostly thinking of team-external factors, though.

    Within team, it's mainly about one specific colleague's work. I've voiced issues and frustrations, to them, teammates, and HR. Nothing fundamentally helped, though. By now, I try to act and think in damage-control mode. To not waste too much time and effort or mental capacity on their work. Still a waste to go through review iterations you feel are useless and wasteful, that they should have noticed and solved beforehand on their own.

    Only once have I used harsh, blunt wording in an email to an admin after prod was down yet again, and there was no upfront or at any point communication regarding that they made some changes. It didn't have a lasting (negative) effect, at least.

  • source
  • hideshow 2 child comments
  • [–] 2 points 2 weeks ago (1 child)

    I'm dealing with similar issues except it's most of my team.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 5 points 2 weeks ago*

    In my previous job, if I was angry, it wasn't at my colleagues. It was at upper management. My colleagues were in the trenches with me. We suffered together. Being angry at work isn't bad in itself, imo. I did use that anger as motivation to get another job. I felt incredibly lucky to do so, however.

  • source
  • [–] 5 points 2 weeks ago

    Flips table

  • source
  • [–] 1 point 2 weeks ago (1 child)

    Yeah there's no need to get angry. It's just a job. If it doesn't work without anger you can always get another one (or probably most people here can anyway).

  • source
  • hideshow 2 child comments