3 ms·
I believe this has already been done extensively. It is called "outsourcing". For many companies this didn't end well. One of the reasons may be the following:
by vog 10y ago
I believe this has already been done extensively. It is called "outsourcing". For many companies this didn't end well. One of the reasons may be the following:
It is more expensive to control the results than to control the process.
Especially in software development, you need quality assurance throughout the whole process, because checking the results or result modules in a blackbox-fashion may lead to catastrophic results.
I know some programmers who were always able to produce code that fulfils the spec, after a few corrections. But any small change in the spec, and the whole thing falls apart. Show them their own code a few weeks later, and they won't be able to maintain it. Leave them alone a few months with their code, and they will refuse to work on it anymore, because they literally can't make any sense of it anymore.
- Roboprog 10y agoAmen. E.g. - I had to pick up a project after these 2 guys in the place I was at in the late 90s that solely survived on the skills of the (rather good) QA in the project. Alas, it was a C program, and any significant change in the (batch) input data would cause the thing to dump core. I'm not blaming the QA for failing to provide all possible variations of the client data (spec???), just the chumps who couldn't do "defensive programming" (e.g. - I/O error or null pointer checks) Leaving these guys unattended for any length of time would be a disaster.
- apatters 10y agoVery very insightful, can't upvote this enough.