Refactoring

The Pragmatic Programmer (Hunt) Refactoring (Folwer)

Hiya, I'd consider these books/articles/podcasts: * Secrets of Consulting by Gerald Weinberg: http://geraldmweinberg.com/Site/Consulting_Secrets.html Every problem is a people problem. * Refactoring by Martin Fowler et. al: https://martinfowler.com/books/refactoring.html talks about how and why to refactor, as well as providing a nomenclature for the process. * Code Complete by Steve McConnell. https://stevemcconnell.com/books/ A bit dated (the last version I could find was from 2004) but a great overview of the entire software process, from requirements to maintenance. * The Mythical Man-Month by Fred Brookes: https://www.oreilly.com/library/view/mythical-man-month-the/... (https://www.oreilly.com/library/view/mythical-man-month-the/0201835959/) best practices about software development, written about a project from the 1960 and 1970s. * The Joel On Software Strategy Letters: https://www.joelonsoftware.com/2000/05/12/strategy-letter-i-... (https://www.joelonsoftware.com/2000/05/12/strategy-letter-i-ben-and-jerrys-vs-amazon/) is the first one. All of them (I think there are five) are great.…

Refactoring by Martin Fowler. He takes you through a piece of code and refactors it all into smaller and more usable parts explaining what he's doing along the way. He does this with two difference pieces of code, if I recall correctly, then the third part is an index of all possible refactors. I read it cover to cover in less than a week and has totally changed the way I program.

Code Complete seemed to be a book with a lot of dense, redundant content. Reading what was written had me feeling like I was reading information that could have been written by myself. Clean Code on the other hand (along with Refactoring by Martin Fowler) changed the way I write code for the better.

Upvoted, and I would also say the Book of Mormon, with the Bible. The BoM reinforces the Bible's teachings powerfully, and as I age and read again, sometimes in other languages, and some scholarly things about it, they both just keep getting better and better. Including in their effect on me. You can get a copy of either one for free. Edit: Additionally, some which have been mentioned or not: - a couple of biographies of Lincoln (one is free on gutenberg.org, the other more recent by Doris Kearns Goodwin), and one of Washington whose name I forget now, but there are good ones out there. - the 7 Habits book (Covey), and How to Win Friends and Influence People by Carnegie. - Refactoring ..., by Martin Fowler. - some thick Scheme programming book from college (sorry, it's downstairs). And "The Little Schemer", also about Scheme (one of the authors, Friedman, was also our instructor). - Since Cumorah, by Hugh Nibley (maybe dated now, but there is a lot of related work). Really got me interested in related topics.

- The Pragmatic Programmer - Refactoring - Facts and Fallacies of Software Engineering - Code Complete

Smalltalk Best Practice Patterns by Kent Beck. Refactoring by Martin Fowler. Design Patterns by the Gang of Four. Domain Driven Design by Eric Evans.

Refactoring. If I could shove that book down every coder's throat in the world I would. Or, if I could even just get them to use extract method like ... half the times they should I'd consider that to be a major historical achievement.

Refactoring by Martin Fowler. Extremely practical if you work with old and large code bases.