#Bleeding edge tech update#

Sit too long in a 'field tested' technology and good people might move away (not to mention that there will always be people who prefer familiar technology who refuse to update their knowledge).

It might be hard to get qualified resources with bleeding edge technologyįrom a developer perspective, I do not see a reason not to get hands dirty with some new technology (in your spare time) but he/she might be limited to open source/free ware/developer editionsįrom am organization perspective, it looks like its a double edged sword.

Supporting a new (or for that matter a different technology) would require additional resources

The new technology might not be supported by the organization.

Standards might change and significant rework might be needed to make the project adhere to standards.Choosing the field tested technology will save these efforts

convoluted solutions might lead to more problems during maintenance phase and the application might become a white elephant Will cut down development time/cost and make maintenance of the code base relatively easyĪrguments for picking field tested technology/against picking a bleeding edge technology.It will give better user experience (May be HTML 5 for videos, just a thought).Sometimes latest technology is backward compatible and only get to gain the new features without breaking the old functionality It might overcome some of the limitations of the existing technology ( Think No SQL vs RDBMS when it comes to scalability).Net vs PHP) when you are planning for a new project /maintaining an existing project in an organization.Īrguments for picking the latest technology How do you pick a technology ( am not talking about Java vs.

I have been pondering about this for some time.

Bleeding edge tech