Self-review your code

Rice harvest on Louisiana farm by Karl Wiggers

Something really resonated with me in the latest episode of the Under the Radar podcast: the concept of switching context and reviewing your own code before committing.

I’m really happy to hear @marcoarment and @_Davidsmith discuss how they review every commit to validate all code that goes into version control.

I often have a hard time selling this habits to junior devs (and even senior devs!). As a consequence I’ve often been rewriting git repository histories to remove passwords, PII1, zip files of several hundreds of megabytes (“git is so slow”) and even malware.

I like to rethink my code architecture while reviewing and often go back to refactor, to take more edge-cases into account or for simplicity.

I love using Fork for this, a great git UI with a good diff viewer, all in one app.

  1. Personally Identifiable Information, you want to be careful with that ↩︎

Picture: Rice harvest on Louisiana farm by Karl Wiggers

Comments

Leave a Reply