Tidy First? by Kent Beck captures the spirit of Ousterhout’s A Philosophy of Software Design while also recognizing the inherent tensions of developing software within a team and business. You can also read it in about two hours. Recommended!
A Philosophy of Software Design by John Ousterhout is one of my favorite books on software design. When I heard that Kent Beck had a new book out, Tidy First?, that was deliberately engaging with similar content but a markedly different pedagogy, I knew I had to read it. (It also helped when I realized it’s around one hundred pages and you can read it in a couple hours.)
Building from there, Beck builds out an approach to software where you think deliberately about separating and sequencing changes that “tidy” (modify structure) as opposed to changes that modify application logic.
Any book that can force you to reconsider a somewhat strongly held belief, particularly after spending a fair amount of time in industry, is doing something right, and Tidy First? is certainly in that category.