<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software Design on</title><link>https://eunus.dev/tags/software-design/</link><description>Recent content in Software Design on</description><generator>Hugo -- gohugo.io</generator><lastBuildDate>Thu, 25 Dec 2025 00:00:00 +0600</lastBuildDate><atom:link href="https://eunus.dev/tags/software-design/index.xml" rel="self" type="application/rss+xml"/><item><title>How Thinking About Tests First Can Boost Your Code Quality</title><link>https://eunus.dev/blog/how-thinking-about-tests-first-can-boost-your-code-quality/</link><pubDate>Thu, 25 Dec 2025 00:00:00 +0600</pubDate><guid>https://eunus.dev/blog/how-thinking-about-tests-first-can-boost-your-code-quality/</guid><description>One piece of advice I frequently give to junior developers is:
Write code that is easy to test.
Interestingly, my goal isn&amp;rsquo;t to increase test coverage. My goal is to improve code quality.
Over the years I&amp;rsquo;ve noticed something consistent: when developers actively think about how they would test a piece of logic — before they write it — they naturally write better code.
They create smaller methods. They separate responsibilities.</description></item></channel></rss>