Hands down biggest coding distraction has got to be Project Managers.

Some of my agile projects changes to waterfall from the middle of the project and vice versa idk how. Fuck this life.

I've only met one project manager I'd work for again ... but he moved companies.

I got sucked into PMing for a while and I hated it. And @runfrodorun is correct - agile is buzzword nonsense. Also, I'd sooner smash my junk with a tack hammer than be a PM again.

The problem with Agile is that businesses think they can apply it to individual teams and say "hey we are doing agile". The critical flaw there is that you dont DO agile, you BE agile. Agile isnt something you can just apply to a few teams and keep everything else the same. It requires structural changes across the whole organisation, and therefore most businesses will never do it properly because they insist on keeping all those middle managers that they dont need anymore. They dont want to restructure the whole company. I work on a team that is apparently "agile", yet the project still has a QA department. If you have agile teams, there shouldnt be anything for a QA team to do because the testing is part of the development process. Agile is a good idea based on solid principles but unfortunately it requires a level of commitment to change that most businesses are not willing to give it.

Some developers are so agile, that nearly all development comes from customer calls and bug tickets.

I would call that support driven development (SDD)

@randomcomma Same here. Got sucked into it and hated it. That is a horrible job and I have no idea how people do it without being miserable the entire time.

I think the problem with is with the common understanding of agile.

agile is a mindset. It's about working the best way that suits your team, your needs, and your business. If you try to "do agile" as per some template or the same as some other team in some other company - it will be shit.

Also the whole business has to buy into it, not just a Dev team or two.