4 ms·
Of course, the question is loaded. You're assuming that they will be adding developers who have no familiarity with the project. Project resources have lifecycl
by DannoHung 16y ago
Of course, the question is loaded. You're assuming that they will be adding developers who have no familiarity with the project. Project resources have lifecycles, especially for larger ones. If you have, say 200 developers on a project at the start and as the project reaches maturity, you reduce that amount to 50, those 150 other developers don't magically forget everything overnight.
So, if six months down the road, you need more dev resources because you're falling behind a little, adding some of those devs back will probably help speed things up. Notice that the company that added the devs in the story has 400+ heads already. What they could be doing is hiring new guys to take on some of the non-exchange related work they were doing and shifting some project-experienced devs back on.
Of course, that's the best possible scenario. What they're probably gonna do is just fuck things up.
- arethuza 16y agoNice people don't use the word "resources" in that context :-)
- DannoHung 16y agoCritically thinking people don't harp on word choice while ignoring the argument.
- arethuza 16y agoActually I accepted your argument (and upvoted) - just the use of "resources" like that is something I hate... (Note the smiley on my comment).
- protomyth 16y agoyep, never ignore the actual argument based on word choice, but word choice might give you a rather large clue on the mindset of the people making the argument.
- pmjordan 16y agoThe article also alludes to "open source developers" - this could be interpreted such that they're bringing on developers who already work on specific OSS projects to do specific integration/debugging/optimisation work. But who knows, the whole thing is pretty damn vague.