How to build toxic software teams
badsoftwareadvice.substack.com
How to build toxic software teams
1–10 of 102 posts
Re: How to build toxic software teams
#2Re: How to build toxic software teams
#3Re: How to build toxic software teams
#4Re: How to build toxic software teams
#5Re: How to build toxic software teams
#6It's easy. Hire one bad narcissist. Keep praising and promoting them.
Re: How to build toxic software teams
#7With the industry wide layoffs this feeling has only gotten worse now that there is a decent chance that accepting blame (or your manager deciding the blame is on you) will be the difference between having a job or not in 6 months.
Maybe this is unavoidable given that these processes only kick in when something goes wrong, and you can only screw up at your job so much until you get shown the door?
Re: How to build toxic software teams
#8It's easy. Hire one bad narcissist. Keep praising and promoting them.
I've ended up leaving it for people who are attention-seeking, in common culture it is reduced to "people I have conflict with who I don't think care about other people", which has some irony, that's how a narcissist would perceive many interactions.
Re: How to build toxic software teams
#9Make sure to monitor your team every day and force their performance first thing in the morning. Focus on the daily grind to ensure meaningful change can never occur.
Hire randomly
Never put in the work to identify potential candidates based on their contribution to the industry or relevant projects. Always rely on blind applications to a job ad then make the applicants perform grueling and humiliating coding tests until they've successfully demonstrated their pain tolerance and allegiance.
RTO
Make your developers as uncomfortable as possible and force them to move to the most expensive real-estate market possible. It's important to remind individual contributors of their position on the social hierarchy. Home ownership and starting a family is for execs only.
Re: How to build toxic software teams
#10I do wonder if people have any experience around doing root cause analysis that doesn't just end up in blame games? I've worked for three companies in a row that claim to have blame-free cultures, and all of them did put work into it (structuring the documents to not assign an individual's name to any given misstep and telling people to be kind and understanding). But in every case, you can feel it in the air that ev…