This book is about the famous State of DevOps Reports; some kind of recap from years 2014-17. In this blog post I've summarized what are the impacts of continuous delivery according it. "Continuous delivery improves both delivery and performance quality."
This is a book about how to detect bad code from code base with the help of code's history from git. I was surprised how simple things and techniques book uncovered about code quality. The key point is the time. We shouldn't do just static analysis from our current code but analyze how our code has lived and progressed. Tornhill calls this behavioral code analysis.
I will explain some interesting things from the book, like hotspot analysis and what are surprises in code and why they can be really expensive. After reading the book I understood how to improve code quality cost-effectively.
I wrote a book review of The Clean Coder by Robert C. Martin ("Uncle Bob"). It tells what makes programmer a professional programmer and gives practical advice. Professional programmer takes responsibility for his/her work and improves himself/herself constantly. Someone who cares about his/her career as a programmer. The book is relatively short (210 pages) and easy to read. I recommend it to all software developers. My rating: 4/5.
This was really interesting and educational book about functional programming. What makes this book really good is that it is really practical.
I wrote about what was most interesting in this book. And how it opened my eyes that functional programming is useful even for object-oriented programmers like me.
I deeply recommend this book to every C# developer.