I learned a lot about good software design from Structure and Interpretation of Computer Programs. It's free and has 350+ exercises. I just committed to doing o

I learned a lot about good software design from Structure and Interpretation of Computer Programs. It's free and has 350+ exercises. I just committed to doing one a day for a year. I learned so much from that book it's like I aged ten years in that one year. Revolutionary for me. I also loved - Designing Data-Intensive Applications - Design Of Everyday Things I've got a list of other influential books with my thoughts here: https://deliberate-software.com/page/books/ https://deliberate-software.com/page/books/ My controversial takes are that the whole series of Domain Driven Design books are pretty poor. I've seen several teams fall into a mud pit of endless meetings arguing about entities vs repositories. Same thing with Righting Software. The books are all filled with vague statements so everyone just spends all this time debating what they mean. It turns teams from thinking critically into religious bickering. Same for all the design patterns books.