Lack of vision and lack of decisiveness. A "we'll cross that bridge when we get there" attitude for everything. No clue about the tech stack and no direction causes the programmers to, for lack of a better word, start working randomly, and it's no surprise the code will look like an ant colony. Bad design decisions go undetected, and when someone does bring them up, management has no clue what to do about it. In fact it is really too late by then.
There's a guy who is on the spectrum. Terrible communicator. But understands pretty much everything about our code.
There's a guy who doesn't understand shit, doesn't know software engineering terms, and feels the need to redo everything his way (so that he understands. He admitted so when I called him out).
There's a guy who gets shit done, but there's always a couple of issues with it that reveal themselves later that have to be iterated on, back and forth.
There's me, I need some central directives and direction. Right now the rewrite-guy is always breathing down my neck and second guessing the way I have my microservice set up, despite not understanding the external API problems I have to design around.
Would love a manager/tech lead that could actually just do something useful with this situation rather than faff about. The tech lead is present for all of this, and sees all of it happen, but never really interjects or involves himself. There's never resolution, unless you really push him for it.