|
|
Tue Apr 30 13:16:24 GMT 2024 legacySometime dailywtf share not only funny stories, this is also a meaningful one, I really not sure if it really silly to put so much effort to make old cobol work - http://thedailywtf.com/forums/thread/97990.aspx Here is a sample of how to put a legacy swing application under automated test - http://www-128.ibm.com[..]operworks/java/library/j-legacytest.html Experience of porting COBOL code to Java - http://blog.objectmentor.com[..]7/05/16/pack-rats-are-running-the-asylum Martin Fowler suggestion about working on legacy system: replace it bit by bit - http://martinfowler.com/bliki/StranglerApplication.html A lot of managers and developers I know believe http://blog.objectmentor.com[..]2/13/business-software-is-messy-and-mgly , how about you? I think every software have room to improve, but if we work hard enough to make I, and other, life easier, thing will get cleaner and cleaner Notes for studying "Working with Legacy code" - http://www.markhneedham.com/blog/category/book-club/ Tip for handling legacy software, I think the most important one is focus on delivering immediate value - http://www.infoq.com[..]ips-to-developers-starting-on-large-apps Uncovering the Seams in Mainframes for Incremental Modernisation - https://martinfowler.com[..]ReplicationToEnableNewProductDevelopment (google search) (amazon search) second |