This is not a post on a technical topic, but rather on a common pitfall for engineers – we like to point out something wrong the moment we see it. Understandably, we are very good at it. We are basically trained for it. When it comes to code reviews, or design reviews for complicated distributed system protocols, we want to be able to spot flaws as quickly as possible. Habits are usually formed with three factors – trigger, behavior and reward. It’s the same thing that drives the “feel sad” -> “eat chocolate” -> “feel good” cycle. For engineers, the cycle is “see a problem” -> “spot flaws” -> “feel