Bookshelf update — September 2026

Thu, 10 Sep 2026 14:10:52 +0200

I haven’t updated my book list for half a year. So, here is what I’ve read recently and can recommend — there are some gems in the list.

1. Unit Testing Principles, Practices, and Patterns — V. Khorikov

Of all the titles in the list, this impresses me the most. Despite the name, it covers all types of automated behavioural tests: unit, integration, and end-to-end. It changed my approach to code organization and my view of which tests deserve a place in a codebase. The book is also helpful in today’s drift towards agentic coding, guided by spec-driven development and TDD.
Link to the book

2. Fundamentals of Software Architecture — N. Ford

Software engineering is often described as a craft. One reason is the many decisions developers make based on what they once saw, heard, or practiced. I believe that proficiency comes with awareness of all possible tools. Awareness turns choices into deliberate informed decisions. This book explains software architecture methodology and provides the starting set of tools for architects.
Link to the book

3. C# 12 in a Nutshell — J. Albahari

A great source for exhaustive knowledge of C#. It reads better than I could expect from a book focused on details of a complex language. Still took me more than a month to complete. Again, awareness of internal functioning and available options leads to elegant solutions, efficient and maintainable code. Definitely a must read for senior-level C# developers. I also tried ‘Pro C#’ by A. W. Troelsen, but its 1600 pages found my head to be too small for comfortable living.
Link to the book

4. ASP.NET Core in Action — A. Lock

This book is much harder to read than the previous one. It is not supposed to be read from start to end — and I had to shortcut my reading process and skip some sections. For those starting with ASP.NET, selective reading provides a good explanation of how things work and many code snippets ready for use as starting points.
Link to the book

5. Accelerate — N. Forsgren

My science-inclined heart fills with joy when I see a properly designed longitudinal study with a powerful sample size in the tech industry. The study is a solid justification of DevOps practices in software development. A logical relation is the one between software delivery performance and performance-focused organizational culture. The interesting part is that implementation of DevOps is highly likely to transform the culture as well, despite the latter is a much broader concept.
Link to the book

6. On Writing Well — W. Zinsser

Clarity of writing means clarity of thought. This book does not provide exact writing instructions, but enables freedom and desire for writing — in any style, about any subject. It is a relaxing, slow, and amusing read, breaking the line of a tech reading list. Although it put my vocabulary to work: many words come from non-fiction world of American literature, which I rarely encounter in technical media.
Link to the book

Book review: “The Object Oriented Way”, Christopher Okhravi

Mon, 22 Sep 2025 15:53:41 +0200

Last week I finished reading “The Object Oriented Way” by Christopher Okhravi. I was attracted to this book with occasional posts by the author on Youtube where he was discussing complex and interesting topics of OOP. His dives into use cases for composition vs. inheritance, composition patterns, and dependency inversion finally convinced me to buy a full copy. I was not disappointed!

This book is like a Bible of OOP. It starts from the very foundational topics like syntax, declaration vs. assignment vs. initialization, number types, variable mutability and so on – written in a concise yet exhaustive manner.

The story develops with detailed discussion of all the tools used in C# OOP, each chapter more advanced than the previous one. It culminates with very interesting discourse of Liskov Substitution Principle: covariance, contravariance, invariance, and the limitations C# has regarding pure logical object-oriented compatibility.

The ending was somewhat unexpected. For me it turned a textbook into a wonderfully written story, with a narration gradually building cognitive tension towards beautiful complexity and then resolution with a new state, a level above the starting point. I will not spoil any details, though :)

Whom this book is going to be useful:

anybody who wants to learn C#
junior devs to build a solid understanding of OOP toolchain
middle-to-senior devs to fill in the gaps in OOP theory
staff devs and above to master arguments for or against object-oriented approach in a particular module

Verdict: 4.5 / 5 – essential.
Consider buying the full book. It is a worthy investment for most of OOP practitioners.

I personally would love to see more detailed UML diagram section. They can be quite complex, and it would be cool to have a complete material on how to write expressive diagrams when planning OOP architecture.

Blog — George Mishurovsky: posts tagged C#