I can't make out what he was paid for "rushing things out." If it's the same as other programmers, then that reflects badly on the managers.
I've seen managers citing low profits for low salaries, but never want to give out the lion's share when the company turns huge profits. Then, programmers become cheap commodities who can be replaced. Cost is always the bare minimum you can get away with, regardless of the profits.
This is more prevalent more in the local corporate companies of my country than start ups.
I can't stress the importance of how some corporate managers hardly know anything about the technicalities, and end up agreeing to outrageous changes in the requirements. This is the problem in IT companies that engage purely in "pricing wars." And the thing is, most of these mangers don't even have the necessary communication skills, for that's all they have to do, right?
I've seen managers citing low profits for low salaries, but never want to give out the lion's share when the company turns huge profits. Then, programmers become cheap commodities who can be replaced. Cost is always the bare minimum you can get away with, regardless of the profits.
This is more prevalent more in the local corporate companies of my country than start ups.
I can't stress the importance of how some corporate managers hardly know anything about the technicalities, and end up agreeing to outrageous changes in the requirements. This is the problem in IT companies that engage purely in "pricing wars." And the thing is, most of these mangers don't even have the necessary communication skills, for that's all they have to do, right?