<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Refactoring on wid's blog</title><link>https://wid-blog.github.io/en/tags/refactoring/</link><description>Recent content in Refactoring on wid's blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 28 Feb 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://wid-blog.github.io/en/tags/refactoring/index.xml" rel="self" type="application/rss+xml"/><item><title>Ad Fallback Server Design Retrospective</title><link>https://wid-blog.github.io/en/posts/career/dable/ad-fallback-server-retrospective/</link><pubDate>Wed, 28 Feb 2024 00:00:00 +0000</pubDate><guid>https://wid-blog.github.io/en/posts/career/dable/ad-fallback-server-retrospective/</guid><description>Designing a Nest.js-based fallback server while removing a legacy ad server. Why a horizontal layered architecture fit better than Nest.js&amp;rsquo;s default vertical module slicing for a single API with complex business logic.</description></item></channel></rss>