Using a ChangeLog

A good practice I have done since my early days at University is to keep a record of notable changes I make to a project or “thing”. In computing this is super common as changes you make, often to code, don’t work the first few times, so you want to record what you changed to un-break it. The recording is a simple text file which is universally called a “ChangeLog“.

For example during October I changed our online shop shipping costs from being £3.50 to FREE. I have no hope of remembering I did this in a few months time so I make a note of it in my ChangeLog – I write these into evernote but you can use whatever you like. I write each change as follows:

  • Text documenting the change
  • Name of person making the change if using a shared ChangeLog

In addition to the ChangeLog being useful for my own projects I find it very helpful for my regular 1:1s with my boss/teams, workshops and even when preparing for job interviews.