this post was submitted on 22 Aug 2026
73 points (89.2% liked)

Programming

28239 readers
153 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 3 years ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] Kissaki@programming.dev 4 points 1 day ago (1 children)

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.

[–] thedeadwalking4242@lemmy.world 1 points 1 day ago (1 children)

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

[–] Kissaki@programming.dev 1 points 1 day ago (1 children)

That sounds like it's unmaintainable. No chance to guard against (severe) consequential issues(?).

It's insane, I've burned the candle at both ends, I'm looking for a new job now