The long way through Software Craftsmanship

Brown-bag session: refactoring legacy code

Jul 1, 2015 - 1 minute read - Comments - refactoringlegacy-codetrainingbrown-bag-sessionclientlegacyslidespresentation

Today I have done a brown bag session about refactoring legacy code. It includes:

  • legacy code definition. There is no agreement about this in the team.
  • the legacy code change algorithm (source is Feathers, Working effectively with legacy code). Plus an example about it.
  • working with legacy code
  • experience with it.

The slides are available here (PDF format)

We also did a practical session, whose experience report is here

Disclaimer about AI/GenAI

As of 2026-05-06, the text in these articles and blog entries has been written without AI/GenAI, except I sometimes use a spellchecker to fix errors. Think Word's spellchecker, not ChatGPT.

Notes, as of today (2026-05-06):

  • No code snippet has been automatically generated, nor vibe-coded, nor generated and reviewed.
  • I don’t have any article with AI contribution.

For future entries:

  • I may have used GenAI for the code in the repo. The code I exemplify/copy in the article will always be reviewed and tested, not vibe-coded. I will specify it in each snippet or at the top/bottom of the article.
  • I normally don't use it for the text contents, although if I have used it for the article text, it would be indicated as such.

Any entry before 2026-05-06 does not contain any AI/GenAI.

For more information, read the AI/GenAI Policy

Self-study in July 2015 Iterate with index in clojure