Live data from Hacker News

How to build toxic software teams

badsoftwareadvice.substack.com

101–102 of 102 posts

Re: How to build toxic software teams

#101
I actually wrote a similarly tongue in cheek post a while ago, called "The Unethical Developer's Guide to Personal Success": https://blog.kronis.dev/articles/the-unethical-developers-gu...

I've become more or less convinced that having a positive environment takes a lot of work and it's easy to go wrong - regardless of whether someone is being a bit malicious, or just makes it worse unknowingly.

Re: How to build toxic software teams

#102
post #63

Earlier quoted context omitted.

In reality I know what you mean, but not a good look for you imo. Imagine that upgrade causes an issue upstream and someone has to explain who approved it. There's always a way to get housekeeping items approved, sneaking it in isn't it.

I agree, it was a calculated risk. Without getting into the deets I was confident it wouldn’t introduce any major issues. In fact NOT upgrading had resulted in problems that affected production a few weeks prior. Would I recommend a junior engineer yolo it? Of course not. But I’d also warn junior engineers to always keep a healthy skepticism when they are told “No, this cannot be done.” > There’s always a way to get…

> I did my best to make the case from a technical (bug fixes and features), business (vendor X won’t support us on this version), and customer (customer wouldn’t be happy if they knew we were running version X) standpoint.

I feel your pain then.

Post reply on HN