Once you are a developer, you will notice something interesting during [[Code Review]]: > Time spent (comments) on discussions > - trivial CR will contain 100 comments, > - while 100-file CR will contain 0 comments and 2 approves ^example #compose my story of my 1st code review where I was nitpicked for a sport We can simplify it to a principle that I call `The Nitpicking Effect`: > The easier a change is to understand, the more nitpicking it attracts. #produce a picture that presents a similar effect like [[Goodhart's Law]] There are a few reasons for that matter. ## Hidden effects ### [[Bike Shed Effect]] ![[Law of Triviality#^definition]] So in other words, when there is a trivial dispute, like [[If else, switch, or strategy]] in one file, everyone will add their opinion, as everyone understands these structures, but have different experience, and therefore opinions (and additionally context awareness), what will lead to long discussion. But once there is a discussion of a complex business logic, or 100 small changes (or fixes :D) on many files, that require more knowledge or context awareness - **people will quickly approve**. ^complex-cr ### [[Sayre’s Law]] ![[Sayre’s Law#^definition]] This is more interesting scenario, where except knowledge or experience, an ego enters, and someone tries to prove themselves. Moreover, it doesn't seem to be experience related. ## [[Goodhart's Law]] #compose