Freelance software grandad
software created
extended or repaired
Follow me on Mastodon
Applications, Libraries, Code
Talks & Presentations
Listening to Sticky Wickets, the new album by The Duckworth Lewis Method. It's rather lovely and this review at The Quietus explains why.
My Java "modernisation" guidelines thus far :
Compare and contrast - Boom Boom Afridi vs Boom Boom Mancini.
Of course you're digging around working with old code, it's because you want to change it in some way so all the usual software stuff applies too - do the simplest thing that could possibly work, refactor mercilessly, you ain't gonna need it, once and only once. Lean on your tests and write new tests as you go. If there aren't any extant tests, you've got to go a bit more carefully but you can still write tests to capture existing behaviour before you go changing it. In my current case, there are plenty of tests for some parts of the system and they've been very useful. Other parts of the code are less well served. I've added approximately twice as many tests as I've removed and I'm doing ok - I've put some good new stuff in and not obviously broken anything yet.
Freelance software grandad
software created
extended or repaired
Follow me on Mastodon
Applications, Libraries, Code
Talks & Presentations