2 ms·
>(e.g., picking a toolset, or outsourcing a project, or simultaneously fixing resources, scope and schedule) My company had non-developers make these decisions
by spamizbad 15y ago
>(e.g., picking a toolset, or outsourcing a project, or simultaneously fixing resources, scope and schedule)
My company had non-developers make these decisions and we paid the price. We were an org of PHP and Python developers "forced" to switch to C#/.NET (At the request of two technical-ish, but non-developer VPs) It really sucked because the teams expert knowledge got wiped to zero and we had to spend several months learning new tools while also keeping our original deadlines. At the time, I jumped at the opportunity to explore something new. Ultimately however, it was bad business and continues to cost the company money as nothing we were doing received any direct or indirect benefit from being done in .NET. The only difference was we worked slower and produced more defects.