Building for the Next Dev: My Personal Rules

When I leave code for another developer, I try to leave the reason for the surprising bits too. A workaround without its context looks like something that can safely be tidied away.

Names and straightforward control flow do most of the work. A short comment can cover what they can't: an external constraint, a decision we considered, a behaviour that needs preserving. I also appreciate instructions that actually get a fresh checkout running.