agriculture | asatru | copywrongs | humor | musings | politics | technology | index haxton.org  
   
MacRaven Logo
MacRaven
Dave Haxton's Weblog

Musings, Reflections, Rants and Comments from a Hoosier Heathen husband, father, grandfather, farmer and software engineer. There's really only one of me ...


Contact Me   


RSS Feed   


September
Sun Mon Tue Wed Thu Fri Sat
 
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30        



The Blogroll
A Mindful Life The Accidental Smallholder Asahel's Search Austro-Athenian Empire Brad Spangler DiRT Dispatches Garden of Thought Hardscrabble Creek The High Seat Knit Together Laudator Temporis Acti Little Heathen Fox Lorrie's Livejournal Masson's Blog Mutualist Blog MyAppleMenu nobody asked, BUT NoNAIS Notes on Religion Numenous Thoughts OrangeGuru Overlawyered Prophet or Madman rogueclassicism Secular Blasphemy Sugar Mountain Farm TMN Thud Factor Wildhunt Blog within the crainium

Page Loaded at

Eastern Standard Time

Support Denmark!

No NAIS!

MLL


lunar phases
 


Click for Thorntown, Indiana Forecast

       

home :: Technology :: Same_Dev_Tools_...yone_.html

Tue, 08 Jul 2008
Same Dev Tools/Language/Framework For Everyone?

Well, this is like saying that all buildings should be erected using only a hammer, and a screwdriver. Very simple. That way construction workers could move easily from one building to the next without having to learn new tools.

The buildings wouldn't look very good, or be very functional, but who cares? We'd save a lot of money on tools and training!

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?"

(link) [Slashdot]

Tue, 08 Jul 2008 06:27 /Technology | 0 writebacks | permanent link