 |
 |
|
06.07.10 The Future Of Development  By Savio RodriguesRedmonk analyst Stephen O'Grady uses Facebook and Twitter as a guide for the future of development. Is your company ready to follow the prescribed guide? In the post "Beyond Cassandra: Facebook, Twitter and the Future of Development", O'Grady reaches the conclusion that since enterprises are beginning to realize that data is their most valuable asset, enterprise IT departments are should revisit their application development methodologies. Specifically, only invest application development resources in applications that will differentiate one's business from their competitor. O'Grady points to the fact that the vast majority of enterprises historically wrote their own CRM or ERP applications, but don't do so anymore. Enterprises are differentiating elsewhere in the business process, or have found ways to differentiate by customizing off the shelf, and increasingly, open source, packages. Some may argue that Facebook, Twitter, Google, Amazon and Yahoo, whose application development practices O'Grady uses to draw his conclusions are, frankly, a little different than a typical enterprise. But, these firms built strong businesses using development methodologies that have trickled down into the typical enterprise. The use of open source, the emphasis on good enough, or the notion of convention over configuration, or the use of dynamic scripting languages, are all finding their way into a traditional enterprise. These development trends grew out of web native firms. If next generation enterprise application development is to resemble the practices of web native firms, O'Grady suggests that your enterprise should be ready to: • Default to Open Source • Use Permissive Licensing • Use Third Party Project Hosting These are three of the five predictions O'Grady makes. Let's consider these three as they will be the most difficult for enterprises to accept. Plainly put, if there is no competitive advantage in developing an application in house, look to open source it using a permissive license into a third party hosting site or foundation such as Github or Apache. A permissive license, such as the Apache License, and external hosting will help others, possibly in your industry, find the application, and fingers crossed, contribute to evolving the application. The end result is that each enterprise using and contributing to the application benefits from spreading the development costs. Well, that's the theory. Putting it into practice is an altogether different issue. This new development model requires a major shift in line of business and IT decision maker mindset. It's one thing to use an open source product, such as Linux or Alfresco, within your enterprise even whilst knowing your competitor is doing the same. It's entirely different to open source, for instance, your custom developed partner on boarding application, and watch your competitor being to use the application also. Continue reading this article.
|
|||||||
|
| ||
-- DevWebProCA is an iEntry, Inc. publication -- iEntry, Inc. 2549 Richmond Rd. Lexington KY, 40509 2010 iEntry, Inc. All Rights Reserved Privacy Policy Legal |
| archives | advertising info | news headlines | free newsletters | comments/feedback | submit article |
