The flip side is that this is helping those developers stay employable.
I thought I was being all nice and responsible with money: keep it on a single server, watch out for memory and CPU, minimize harm to the environment, outsource to maximize use of our limited resources. Now I'm looking elsewhere for employment and I have no "relevant" experience.
In the meanwhile, the clowns who made this mess get to claim J2EE, cloud, HA, VMWare, Redis, Angular.js, Symfony2, and a living client for their resumes, and their product didn't even work correctly.
| A single clueless person in a position of trust with non technical management, an outsourced project and a huge budget, what could possibly go wrong...
If you are in a position to make technical decisions and you choose Symfony2 and don't even consider that you should have a cache or three in place, you should be dragged behind a van by your teeth. Caching in PHP has reached a point where turning it on is as simple as installing a package and setting a flag.
I thought I was being all nice and responsible with money: keep it on a single server, watch out for memory and CPU, minimize harm to the environment, outsource to maximize use of our limited resources. Now I'm looking elsewhere for employment and I have no "relevant" experience.
In the meanwhile, the clowns who made this mess get to claim J2EE, cloud, HA, VMWare, Redis, Angular.js, Symfony2, and a living client for their resumes, and their product didn't even work correctly.