the theory part has a lot of good ideas, not sure if all really that practical in big pipelines but definitely something to think about. The practical part I'm going to do separate since it's all java focused.

Spodziewałam się dowiedzieć więcej

This book was primarily written in java, and indeed seems to sometimes be written specifically for java programmers. Despite this, most the lessons hold true across languages.

I'm extremely glad I read this, if only to have a clear voice of authority I can turn to when deciding on matters of code formatting, variable and function naming, and of code organization. Lots of code examples included to convince you that the declared best practices are indeed so!

Did not win me over. He likes to back his points up with opinions and not much logical justification. His writing seems a bit preachy at times. Still, I could take away a few things from this book.

Just awesome

I found the first few chapters helpful, but found the remainder difficult to follow because the examples were specifically in Java which I don't know. One to revisit once I have more experience of working on large code bases as part of a big team, with more programming knowledge - the concepts just seem a bit too abstract for me to truly appreciate at the moment, and I'm still struggling to understand where the balance lies between perfection vs pragmatism.

1 Clean Code
2 Meaningful Names
3 Functions
4 Comments
5 Formatting
6 Objects and Data Structures
7 Error Handling
8 Boundaries
9 Unit Tests
10 Classes
11 Systems
12 Emergence
*13 Concurrency
*14 Successive Refinement
*15 JUnit Internals
*16 Refactoring SerialDate
17 smells and heuristics