Dont know why some people defend this low skill team.of game programmers Thy have what deserved.
Smart and intelligent people learn from own mistakes. So...
It's not fair to blame the programmers. I get it, I really do, but it also shows a nativity of software development and the entire team behind this title (yes, I am working at a software company, and yes, I should probably be working and not posting
)
The programmers are assigned their tasks.
The programmers are given x-amount of time to get it done.
A team lead may well play a part in how it is implemented.
A Technical director may well play a role in influences HOW it is done.
A Production direction will say how quickly it has to be done ... even if that's an unreasonable target.
Every programmer, every team, every team lead, will have different skill levels and accuracy; everything rolls up to a QC team/process.
Bugs will be searched for, tracked, and then a team will sit down and prioritize which of those - if found - will get fixed.
While the production director influences what won't get worked on due to time/budget concerns.
All of the time a deep management team will be heavily influencing timeline.
A design team (User experience) came up with the menus, options available, and dictated how things would work: "you click this, that happens," "on this menu are options X, Y, and Z"
So at the end of the day, the programmer is but one piece of a large and complex web: he/she is told what to program, when, and how it will work.
You're blaming the guy who wrote the line of code, but not the people who told him how to write it, the fact that he didn't have enough time to write it, the manager who changed his mind half way through, the UX designer who made the decision on the WASD keys, the QC team who missed the bugs, or the team who prioritized what would be fixed and what wouldn't.
At the end of the day - with game development - typically the programmers are the last people to blame.