Code Reviews are a Failure

  • Find bugs further downstream
  • Propagation of Knowledge
  • Team Ownership
  • Double check functionality/architecture
  • Reviews languishing in a “Ready for Review” state
  • Drastic code architecture changes
  • Being “Approved” based on social standing of the developer opening the request

The Opposite of Code Reviews

The opposite of Code Reviews isn’t NO code reviews.

The Advent of Code Reviews

I want to place the blame squarely on GitHub for enabling and promoting Code Reviews, via mostly circumstantial evidence.

  • Actually find bugs further downstream and upstream
  • Propagation of Knowledge throughout the team
  • Team Ownership of a feature
  • Double check functionality/architecture

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Angelo R.

Angelo R.

Tech Enthusiast, Crypto Skepticist, F1 Obsessed