Those that have followed this blog for some time, know that Trifork Amsterdam, and especially its precursors, are not unfamiliar with challenges when it comes to naming.Now that we have been in the larger Trifork family for some time, it does look like our corporate naming challenges have settled down quite a bit. That does […]
Leaving a Java legacy behind
As with a house, software applications require maintenance too. Otherwise, you risk the digital equivalent of rot: bit-rot. Often, the maintenance is done like with a house: Superficially to make it look nice again with a new look-and-feel, a new colour scheme (a paint job) and a few new stock photos. But every once in a […]
3 reasons why your Big Bang legacy replacement will most likely fail miserably!
This morning I was listening to the radio and first, there was an item about a large government organization that had spent 4 years and a boatload of money on a Big Bang legacy replacement. The project was canceled and had been a complete waste of time, energy and money. Right after this item, there […]
Dockerising your legacy integration tests
As most of you will know, every now and then you can expect the question ‘Can you help fix something on this ancient project?’ According to the Universal Software Ageing table, that means anything from last month to much, much older. I got such a question recently, being in-between projects, and this project fell squarely into […]