<?xml version="1.0" encoding="utf-8"?> 
<rss version="2.0"
  xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
  xmlns:atom="http://www.w3.org/2005/Atom">

<channel>

<title>Blog — George Mishurovsky: posts tagged testing</title>
<link>https://mishurovsky.com/blog/?go=tags/testing/</link>
<description>A blog by George Mishurovsky — a senior software engineer with a medical degree. Drawing from both engineering and scientific thinking, he explores software, architecture, design, psychology, and product thinking.</description>
<author></author>
<language>en</language>
<generator>Aegea 11.3 (v4134e)</generator>

<itunes:owner>
<itunes:name></itunes:name>
<itunes:email>george@mishurovsky.com</itunes:email>
</itunes:owner>
<itunes:subtitle>A blog by George Mishurovsky — a senior software engineer with a medical degree. Drawing from both engineering and scientific thinking, he explores software, architecture, design, psychology, and product thinking.</itunes:subtitle>
<itunes:image href="https://mishurovsky.com/blog/pictures/userpic/userpic-square@2x.jpg?1753619610" />
<itunes:explicit>no</itunes:explicit>

<item>
<title>Bookshelf update — September 2026</title>
<guid isPermaLink="false">54</guid>
<link>https://mishurovsky.com/blog/?go=all/bookshelf-update-september-2026/</link>
<pubDate>Thu, 10 Sep 2026 14:10:52 +0200</pubDate>
<author></author>
<comments>https://mishurovsky.com/blog/?go=all/bookshelf-update-september-2026/</comments>
<description>
&lt;p&gt;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.&lt;/p&gt;
&lt;h3&gt;1. Unit Testing Principles, Practices, and Patterns — V. Khorikov&lt;/h3&gt;
&lt;p&gt;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.&lt;br /&gt;
&lt;a href="https://www.oreilly.com/library/view/unit-testing-principles/9781617296277/"&gt;Link to the book&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;2. Fundamentals of Software Architecture — N. Ford&lt;/h3&gt;
&lt;p&gt;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.&lt;br /&gt;
&lt;a href="https://www.oreilly.com/library/view/fundamentals-of-software/9781492043447/"&gt;Link to the book&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;3. C# 12 in a Nutshell — J. Albahari&lt;/h3&gt;
&lt;p&gt;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.&lt;br /&gt;
&lt;a href="https://www.oreilly.com/library/view/c-12-in/9781098147433/"&gt;Link to the book&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;4. ASP.NET Core in Action — A. Lock&lt;/h3&gt;
&lt;p&gt;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.&lt;br /&gt;
&lt;a href="https://www.manning.com/books/asp-net-core-in-action-third-edition/"&gt;Link to the book&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;5. Accelerate — N. Forsgren&lt;/h3&gt;
&lt;p&gt;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.&lt;br /&gt;
&lt;a href="https://www.oreilly.com/library/view/accelerate/9781457191435/"&gt;Link to the book&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;6. On Writing Well — W. Zinsser&lt;/h3&gt;
&lt;p&gt;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.&lt;br /&gt;
&lt;a href="https://www.goodreads.com/book/show/53343.On_Writing_Well"&gt;Link to the book&lt;/a&gt;&lt;/p&gt;
</description>
</item>


</channel>
</rss>