Give Scott Guthrie's post a read : About Technical Debates (and ASP.NET Web Forms and ASP.NET MVC debates in particular)
Brilliant!
We are currently having debates over technologies in our company. The general consensus by “the powers” are that the technologies involved is to “new” and unfamiliar to majority of people implementing them, and thus some projects have burned.
My opinion is that it is less about the new technologies, more about the people that are implementing them (“Bad developers using great tools/frameworks can make bad apps”). A huge topic of debate is around the “new” ORM thing (nHibernate) that we are using - the older generation of intermediate/junior developers do not understand how to use it, regardless of the fact that nHibernate has been around longer that the people that are complaining about it, has been in industry!
I suppose this is an age long debate. From business point of view, do what we have been doing fairly successfully in the technologies we have been using and is well understood. But the risk associated with this is :
1) Losing the A grade developers who are more interested in leveraging technology to solve their problems than needlessly code around problems using the same method over and over again.(ie. getting stuck in a rut)
2) From a technology point of view fall behind industry, start losing the edge, and potentially future productivity enhancements, that could cut costs and time.
Sunday, January 24, 2010
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment