”Ireland is the last country in Western Europe that is still throwing roads ata traffic congestion problem” was one statements I remember hearing from mychildhood. Back then I could not understand why more roads would not solvea traffic problem however as I traveled the world and had the opportunity ofliving in cities like LA, NYC, Boston and London, it became painfully obviousthat more roads was not the solution. The solution then becomes how do webetter utilize the existing transportation infrastructure? Put more simply howdo we do more with less?
Recently at a future of application development conference in NYC a leadarchitect from a world bank echoed these exact same sentiments but this timeapplied to application development. Now this is a major global bank and theirlead architect was telling us that the last thing he wanted, to ﬁx their problemswith application development, was to throw more developers at it. Again on ﬁrsthearing this statement it seems counter intuitive but just like the roads problemabove on deeper reﬂection it makes more sense. The problem, with applicationdevelopment, is the steep learning curve needed to bring these developers upto the point of where they can be productive. Application development, in aradically changing IT landscape, irrespective of the programming model used innot easy. This quickly becomes a problem of managing complexity, a problemthat will only get worse tomorrow as this complexity increases. However as withthe road problem the solution is similar but ﬁrst let us pose the proper question.How do we better utilize and empower the existing staff to be more productive?
To better utilize and empower the existing staff we need to move themto an asset based development model. The maintenance of, reuse of, andenablement of these assets (in this case software development assets) is coreto managing the complexity inherent in application development today. Theseassets need to introduced as early as possible in the life cycle to maximize theirbenefit and their impact and these assets need to constantly be maintained andupdated to help maximize their reuse and impact.
In future blog entries will look to understand the types of assets used in applicationdevelopment and to understand the context in which these assets are used.Using this context as guide, we can suggesting the best asset to be used in a particular context to the end user. In the next entry we will first examine three typical types of assets used in application development today,industry model assets, software patterns assets and legacy assets.
Doing more with less
eoinlane 11000078H8 Tags:  reusable-assets soa consumability assets context pattern asset-consumability patterns content 1,712 Visits