It's probably time to stop recommending Clean Code (2020)
There&#x27;s a lot of bad advice being tossed around in this thread. If you are worried about having to jump through multiple files to understand what some code is doing, you should consider that your naming conventions are the problem, not the fact that code is hidden behind functional boundaries.<p>Coding at scale is about managing complexity. The best code is code you don&#x27;t have to read because of well named functional boundaries. Without these functional boundaries, you have to understand how every line of a function works, and then mentally model the entire graph of interactions at once, because of the potential for interactions between lines within a functional boundary. The complexity (sum total of <i>possible</i> interactions) grows as the number of lines within a functional boundary grows. The cognitive load to understand code grows as the number of <i>possible</i> interactions grow. Keeping methods short and hiding behavior behind well named functional boundaries is how you manage complexity in code.<p>The idea of code telling a story is that a unit of work should explain what it does through its use of well named variables, function&#x2F;object names, and how data flows between function&#x2F;objects. If you have to dig into the details of a function to understand what it does, you have failed to sufficiently explain what the function does through its naming and set of arguments.