Skip to content
A Refactoring Golf exercise
Branch: master
Clone or download
Latest commit 95cc3c4 Nov 13, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
.idea tweak Nov 13, 2018
hole1/src adding golf course (#1) Feb 23, 2017
hole3/src DD - fix name for hole 3 start May 3, 2017
hole6/src DD/IS tidy Feb 24, 2017
hole7/src DD/IS -update totals Feb 24, 2017
.gitignore adding golf course (#1) Feb 23, 2017
golf.iml adding golf course (#1) Feb 23, 2017

Refactoring Golf

Refactoring Golf is a game designed to stretch your refactoring muscles and get you to explore your IDE to see what's really possible using shortcuts and automation.

This repo contains several source trees, or numbered "Holes" based on a single exercise. Each hole carries on from the last for a single exercise - which is the application of a tax amount to a set of monatary amount.

Your goal is to safely and efficiently as possible refactor the Hole-X code to look like the Hole X+1 code. You must aim to do it in as few "strokes" as possible.

A "stroke" is essentially a change made to the code, and every stroke costs you points.

Your pairing partner should carefully score you as follows:

  • 1 point for every change made to the code using a shortcut or automated IDE feature (e.g., an automated refactoring, code template, or Find/Replace)
  • 2 points for every manual edit. Note that a single "edit" could cover multiple lines of code.
  • Double points for every change made while the code cannot pass the tests after the previous change.
  • Zero points for code formatting (e.g., deleting whitespace or optimizing imports).

Allow yourselves a maximum of 2 attempts at each round to determine your best score.


  1. You may find that customising your IDE is useful (e.g. custom code templates, or even custom refactorings.)

  2. If possible, it would be a good idea to have the two versions (Hole X and Hole X+1) of each set of source files open on different machines, as you could easily tie yourself in knots editing the wrong files!

  3. Keep that second machine available as a tooling environment. Writing custom tools (scripts, templates etc) costs you zero points in refactoring golf.

Course records:

These are the best known scores, achieved using IntelliJ:

Hole Best score Notes
1 3
2 7
3 5
4 6
5 10
6 7

Course Record: 38


This exercise was developed with Ivan (@s4nchez). :) Thanks to @ivanmoore and @rchatley for the inspiration. These instructions were mostly stolen from @jasongorman's Refactoring Golf repo

You can’t perform that action at this time.