Bio and Publications

▼
Thursday, May 30, 2013

Legacy Preservation and "Code Modernization"

›
The correct marketing term is "Code Modernization". There are a large number of companies in the Code Modernization business. ...
1 comment:
Tuesday, May 28, 2013

HamCalc -- Preserving the Legacy

›
Wow. The response to modernizing HamCalc was overwhelming. Apparently there are a fair number of people who also think that HamCalc is a...
Thursday, May 23, 2013

Legacy Code Preservation: Language Incompatibility and Technology Evolution

›
It's important to address language or platform incompatibility as consequences of technology modernization. The reason why we have to d...
Tuesday, May 21, 2013

Legacy Code Preservation: Some Patterns

›
After looking at this suite of examples, we can see some patterns emerging. There seem to be several operating principles. The Data Matt...
1 comment:
Thursday, May 16, 2013

Legacy Code Preservation: Why Preserve the DSL?

›
\A Domain-Specific Language (DSL) can provide some intellectual leverage. We can always write long and convoluted programs in a general-pu...
Tuesday, May 14, 2013

Legacy Code Preservation: How Do We Manage This?

›
At an insurance company, I encountered an application that had been in place for thirty years. Classic flat-file, mainframe COBOL. And de...
Thursday, May 9, 2013

Legacy Code Preservation: Why Preserve An Abomination?

›
By the early aughts (2001-2005) Visual Basic had gone from state of the art to a legacy application language. Code written in VB was being...