@MEGAF1UX wrote:
@angrybunnie
54k plus all the "perks" that come from working for bioware (STARTING pay) JUST to be a tester, 84k for software engineers..
@MEGAF1UX, 84K is about what a corporate middle-manager makes. Equivalent devs in good companies make about $100K or more. I make a lot more, but I am a consultant who teaches other devs how to write better code while I teach their managers how to better manage their projects.
@MEGAF1UX wrote:
if bioware said "we will have it fixed by launch" or if ea said "you BEST have it fixed by launch".
Any manager who says "You BEST have it fixed by launch" doesn't understand what got them into a bad situation and is probably part of the problem. Not to say all developers are perfect, but any good manager would see the problem early and either get rid of the bad developer (if he/she is hopeless) or adjust resources to pair them up with someone who can mentor them and improve their code.
@MEGAF1UX wrote:
if people are afraid to speak up they shouldnt have those jobs!
I once was trying to help a Senior VP of Development with his organization, and I told him that people were afraid to talk to him. He responded, "No one has ever told me that." LOL. When people work in a organization where they get pounded for speaking up, they and their coworkers learn not to speak up. The better ones find new jobs and the org spirals downward. If you ever want to get into management, I suggest you read "The Empowered Manager" by Peter Block (or any of his other books).
@MEGAF1UX wrote:
if you are doing a module for a game and it is having problems you need to say something BEFORE it becomes too late to fix
You are 100% correct. Who's to say that they didn't? Maybe they did and were overridden by management. However, the other side of that coin is that with good management and QA practices, the developer shouldn't need to say anything. Transparent development, QA, and management processes should keep managers well aware of project status and quality levels. There is over 40 years of published work on how to manage software development and tools to help. There are automated Continuous integration systems that run unit tests automatically every time you check in code and provide statistics about code test coverage. There are issue tracking systems and automated project boards that let you see up to the minute status. Some good ones are even free.
Generally, developers are more aware and want to work in these kinds of environments. Although, I have seen an uptick in the number of managers who now understand the need for good processes. Good software development processes, and management processes like Scrum and Kanban, are very transparent, so if a project goes off the rails, it means that it was driven off by a management team that did not know what they were doing, cut corners, and operated more on wishful thinking than reality.
As for your comments about EA. You may be right. Perhaps, the problem might be solidly in BioWare's team. Then again, that also means that EA didn't see the warning signs, and they should have.