@MEGAF1UX, a lot of very competent developers get caught up in this kind of crapola because they are in an organization that is poorly managed. You seem to want to blame the developers. I am a big believer in treating people like professionals and listening to your team -- THAT is leadership. Even the best developer cannot make a difference if his or her managers will not listen to, and respect, his or her professional recommendations about schedules, process, and other areas. I have seen it way too many times in my career. Like I said, the good ones give it an honest try, but often end of finding another job rather than try to influence a company hell-bent on 80 hour weeks and unrealistic schedules that ruin people's health and personal lives. The term "Death March" is often used to describe these projects.
On the other hand, a good management team can take a development group that is full of slackers and turn it around by implementing better processes, salvaging people that are salvageable through training, mentoring, and incentives, and by hiring new, more competent people to replace the hopeless cases.
If a release goes really badly, it really is a management issue because they are either not leading, not listening to the professionals that work for them, or they are allowing, or even encouraging, shoddy work -- often because they don't feel empowered to push back at their management, stockholders, or even customers.
I was not thrilled that CD Projekt Red delayed The Witcher 3, but I respect them telling for us that they were not going to ship the game before they felt it was ready. They are saying the same thing about Cyberpunk 2077. Yes, I am a bit of a fanboi for them, but really, my comments are more about the courage and integrity of the management decisions. We can agree to disagree about the game itself. :-)