In _Clean Architecture: A Craftsman’s Guide to Software Structure and Design_, Robert Martin emphasizes that system maintenance becomes easier when exploration ([[Spelunking]]) costs and defect risks are minimized ([Martin, 2017]). Code that is hard to read is also difficult to understand and remember, which increases the likelihood of defects. Considering our cognitive limits, the order in which code is read affects comprehension and retention. Optimizing this order can improve both, thereby reducing the cost of making changes. In _Tidy First?_, Kent Beck recommends declaring and initializing variables right before they’re used, while maintaining data dependencies ([Beck, 2024]). He also advises breaking down complex expressions by assigning subexpressions to variables named for their purpose. Since [[Coding involves reading]], the reading order should facilitate effective reading strategies, similar to those described in _How to Read a Book_ ([Adler & Van Doren, 1972]).