Building for the Next Dev: My Personal Rules

Leave code better than you found it—even if it’s yours.

The next developer to work on your code may be a colleague, a new starter or you after enough time has passed to deny all involvement. I try to leave clear intent, predictable structure and fewer small puzzles disguised as cleverness.

The useful question behind “Building for the Next Dev: My Personal Rules” is what changes in the work afterwards. A sound idea should improve a real decision, not only give us a neat phrase for describing it.

The answer is rarely a universal rule. It is a way of looking at the decision clearly enough to choose on purpose.

Notice what the work is teaching

The most useful lessons often arrive through ordinary work. A choice feels awkward, a conversation goes better than expected, or a supposedly small task reveals something important about the system around it.

I try to make those lessons explicit. Name the trade-off, test the assumption and leave a note for the next time. Reflection is most useful when it changes a future action.

Experience becomes useful when it changes what you do next.

Craft improves through attention. Do the work, notice the result, and carry the useful part forward.

I do not always manage it perfectly. The aim is to make the better choice easier to recognise the next time it appears.