Fire all managers. Fire all managers. Fire all managers.

Did you finish your feature?

@retoor yes

we don't need no water

There are multiple articles on how companies increased productivity and boosted profits by removing management layers.

But that got lost conveniently in the dark of news, because obviously it would.

Replacing all devs with AI is still prevalent even today.

@netikras wym?

This isn't a Beatle Juice film

(Love that film)

AMAB (All managers are bad) (at their job)

@chonky-quiche what's that?

@netikras oooohooh let the motherfucker burn! Burn motherfucker.

@netikras google it

Are you asking for managers to be set on fire 🌚

Honestly my manager is a lifesaver, while it's a pain if he wants a particular feature that's a bad idea. The rest of the time it's great. He keeps corporate clients off of my back, handles all of the bullshit paperwork, quotes, write ups, emails, etc. Would be nice if he handled more of the pointless meetings for me but still.

We sold a product to a telecommunications company back in October, and yet literally nothing is implemented yet. The company in question is ironically bad at communicating for a telecommunications company. They've been passing pointless documents left right and centre between 10 different teams and none of them seem to know how to handle some very simple requests to make use of their SSO, get a domain and a few other bits. Somehow they've managed to email about something pointless every day since October and I haven't had to look at any of it. There have been 4 meetings about 'variable cloud provider costs' despite the fact the product sits on a single VM.

Hey there mate, how is that feature going? The client really needs it ya know.

Firing managers would work great for 3 weeks. Then I think we'd start seeing major problems.

Productivity would slow down as individual devs would be demanded to attend meetings with stakeholders, that they normally could avoid.

The dev team would build features, demo them, and get notified the stakeholders decided to scrap the feature. Because there was a communication mistake and they actually didn't want that feature in that way - but since there was no manager around, we built it under a faulty assumption.

My last post might seem like I'm "manager simping". I get it. I do think some managers are cruft that could be cut. But perhaps there at least needs to be part-time managers.

Thing is I have worked in a team where our project manager quit - was replaced by a lead dev - and that worked in the short term...then turned into that dev saying they had no time to code as all the management duties took up all their time.

(Sure, maybe that was a result of other teams still having managers that booked an excessive amount of meetings - but not sure)