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

Mine is small startups letting devs push code on Friday afternoon. What's yours?

The CIO, or such, that tries to show he/she is the smartest person in the room. It's especially common in the tech interviews. Or the want-to-be tech person whose conversation is a salad of tech acronyms but has very little understanding of what all of them are about. It's about trying to impress the common person since most people are too afraid to ask what they mean and risk look dumb.

People bossing equally qualified and ranked employees around. Weak managers who don't make an effort to address problems and just complain. People who do what they want and then heap criticism on others. Short term decision making. Inability to commit to long term plans. Lazy workers who spend hours on the phone or take the longest breaks and also do very little but talk the loudest. Mercurial people who just like to argue but can never be pinned down on everything. People who just book meetings with no agenda in emails and expect you to commit to things without any prep. People who don't read meeting agendas and relevant documentation before coming to meetings, meaning that they need to be spoonfed. People who passive-aggressively stay silent at decision times and never engage and who then make fuss down the line when it's too late. People whose lives are very clearly not working who give you mediocre surface level advice about what they want to see from you when they're not qualified to offer any kind of therapy or counselling and rather than thinking more deeply about the mechanics of people. Managers who are visiting a therapist/counsellor and regurgitate the advice they heard from their last session to you. Managers who talk about their previous awesome gigs and fantasize about recreating them rather than focusing on the problem at hand. Managers who act like they're not supposed to make 50% of the effort in connecting with employees. People focused on empire building instead of doing the job well.

I can go on.

> Or the the want-to-be tech person whose conversation is a salad of tech acronyms but has very little understanding of what all of them are about.

This must be the person who writes job descriptions.

yeah it has never been worth it so far in my career and I always expend 10x the energy cursing such compromises