Take a photo of a barcode or cover
4.19 AVERAGE
4.19 AVERAGE
Abandoning at about 40%. I liked the first part, but it’s a pretty dry book and repetitive. I want to pick this up again at some later point as there are definitely some good learning gems in here.
I feel like this book is definitely targeted at beginners. Would have been a great read during school, or as a junior dev. I think jumping straight to Clean Code would be my recommendation for anyone with a little industry experience under their belts.
informative
inspiring
reflective
medium-paced
Really good! Useful examples! Well laid out! Features a Game of Throne joke!
Nice to read it and have it. It taught me a clear way of view on my code and by following the logic of the author it's definitely taught technics to refactor my code
Biggest takeaway is to take really small steps when refactoring, which the book demonstrated a lot with detailed examples. A lot of times I felt uncomfortable during refactoring, but now I know it's because that I cut corners and didn't take small enough steps.
The book also "refactors to patterns" a lot, which I found helpful reading immediately after the design pattern book.
The book also "refactors to patterns" a lot, which I found helpful reading immediately after the design pattern book.
Pretty clearly written for such a technical topic as how to structure the nitty of your code. Practical wisdom from a respected coder and explainer. Helped me to better conceptualize what code smells are and how to efficiently remove them.
informative
medium-paced
Not bad. Some of the more important parts (like smells) aren't explained very well (I still have no idea what "insider trading" means). The main key idea that reading this banged into me is that no code will ever remain perfect, and that refactoring will eventually be necessary. Including the opposite of many of the changes was eye openning in this regard; archs that are good for code now will not always be the best choice, and knowing how to change between them is good.
This book took forever to finish! But I did it, that too in 2020.
I think the perfect time to read this is when you have started out and are a few months/years into the tech world.
Many of the refactorings are just common sense but when thinking in terms of maintainable code are quite handy.
If nothing else, definitely recommend reading the third chapter that covers the smells of bad code.
I think the perfect time to read this is when you have started out and are a few months/years into the tech world.
Many of the refactorings are just common sense but when thinking in terms of maintainable code are quite handy.
If nothing else, definitely recommend reading the third chapter that covers the smells of bad code.