What practice by a tech team pisses you off to your core?

Explaining their work to other departments with tech jargon. Admittedly, it doesn't happen that often, but when you've got projects due and are already busy with other work, finding that someone has responded to your query with essentially another language can get pretty irritating. Not to familiar with tech stuff, but what is the issue with letting devs push code on a friday afternoon?

There is no one practice that pisses everyone off to their core, but there are a few things that tend to really rankle tech teams. One of the most common problems is fights or disagreements over code or design decisions. This can lead to resentment and infighting, which eventually hinders team productivity. Another issue is new members who don't understand the codebase or how software functions as a whole. They often end up making critical errors that disrupt operations unnecessarily. Finally, admin tasks – such as filing tickets, reviewing logs, and responding to support requests – can feel like they're taking up too much time and energy when they could be spent on more creative project work instead. If you find yourself struggling with any of these issues on your own tech team or within specific collaborative projects, it may be helpful to speak with your supervisor about the situation for potential solutions moving forward.