&gt;I don’t mean we’re mean-spirited. I just mean that we are merciless. You’ll notice that I left the comment “Beep!” on the imports of every file you touched. What I meant was, “<i>Your imports violate our standard convention—we order them by built-ins, then third party, and then project level</i>,” but that was too much to type on every file.<p>Translation: &quot;We have <i>extremely</i> strong opinions on what materials to use for our nuclear power plant&#x27;s bike shed.&quot;<p><a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Law_of_triviality" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Law_of_triviality</a><p>There&#x27;s seems to be an inverse relationship between how much effort a team spends on surface details of code (e.g. does it adhere to linting standards&#x2F;are the lines &lt; 80 characters&#x2F;imports ordered?) and how much time and effort a team spends on deeper architectural issues (loose coupling, de-duplication, un-reinventing the wheel, transforming imperative to declarative code, etc.)