Avoid Indirection in Code
While the example in the article isn&#x27;t great for making the point I actually agree with the main idea.<p>I understand the arguments for &#x27;Uncle Bobifying&#x27; code but I think, as the article says, there&#x27;s a balance to be struck. It&#x27;s highly likely the next time I see your code (or my code if I&#x27;m coming back to it a month or two later) is when I need to fix a problem with it. While it&#x27;s useful to have it split up into logically discrete chunks with sensible naming these 2-4 line functions far increase the mental load of the code.<p>Given I&#x27;m debugging the code because there is presumably a problem with it I can&#x27;t trust these sensibly named functions to do what they say, I need to check their internals to reason about changes in application state. Though well named functions at least help the maintenance programmer reason about the why they&#x27;re equally liable to code rot as the comments they replace.<p>As in all things there&#x27;s a balance to be struck but I&#x27;d rather see a 20-30 line method than jump between 5 files because someone has read Clean Code recently.