Slashdot Mirror


Same Dev Tools/Language/Framework For Everyone?

AC writes "Upper management of the company I work at recently declared that all new development should be done with a single combination of development tools, language, and framework. The main rationale is that people can be relocated from one group / project to another faster, because they don't need to learn a new environment when they switch. Of course the chosen language / framework used by everybody does not need to be the best tool for the job, but it should be good enough to allow every project to get done. What does Slashdot think about this? Is it OK to use the same development tools and language for every project, instead of choosing what fits best? Will the time saved be sufficient to offset the time lost to the 'not the best tool for the job' environment developers will be forced to use?"

2 of 519 comments (clear)

  1. Re:Standardize the RIGHT tools by Fred+Foobar · · Score: 5, Informative

    That combination is better than just free as in beer... it's also free as in free speech! Subversion, Ant, and CruiseControl are all Free Software.

    --
    It was a really good paper.
  2. Re:Choose them all under one. by Clith · · Score: 4, Informative

    [..] I suspect the advantages are at the administration level (reorganizing, branching, merging, etc).

    Having gone from an svn shop to a Perforce shop, I can definitely say that branching/merging is much easier in svn than in Perforce. Also, the whole "client" concept is a bad alternative to file system state files (i.e. .svn or CVS directories).

    I'm not saying that using the filesystem is the best alternative possible, but it's the least worst right now.

    --
    [ReidNews]