What is your worst "fine, I will do it myself" moment in your team?

Having to make business decisions because the business side of the organization isn’t making any…

By business decisions I mean what features to develop and with what specs etc. It’s like our dev team has been left to fend for ourselves…

@100110111 what? With this knowledge you can actually start your own business.

Getting my hands dirty with every task from the rest of the team for a couple of sprints as the other guys were too overwhelmed and afraid of the size of the company and the amount of microservices. I was as well, but getting frozen with fear is not my cup of tea and I think this might have helped them being a little less insecure

Note: I'm the least experienced of the entire team

A lot of code cleanup scenarios. And performance issues. And some styling improvements because most devs can’t and there’s only one overworked designer guy.

I stopped doing the extra work when I realized they never bothered to look at the tickets, let alone merge them in.

Had an open ticket to get a package upgraded for three months.

The team responsible was dragging their feet and my non-technical manager at the time wanted to make absolutely sure that it was *this* version because they read online about xyz...

While on the 11th weekly call to discuss this I went in and deleted one of the dependencies from the environment. Erased my trail, informed the group on the call that the app was down.

After about 30 minutes of nobody finding the problem(idiots) I said we should just upgrade the package.

It worked, we upgraded to latest, and nobody was the wiser.

Technically I didn't do it, but technically I made it happen.

I'm responsible for the database, and I'm getting myself on frontend because that shit just isn't working and it won't get fixed by others

@johnmelodyme probably could. Not interested, though. Starting my own business is one of the things in the world I’m least interested at.