<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Anti-Corruption-Layer on Scholion</title><link>https://scholion.thluiz.com/tags/anti-corruption-layer/</link><description>Recent content in Anti-Corruption-Layer on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Tue, 06 Oct 2026 04:20:06 +0100</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/anti-corruption-layer/index.xml" rel="self" type="application/rss+xml"/><item><title>SOLID Code for SOLID Reasons</title><link>https://scholion.thluiz.com/notes/solid-code-for-solid-reasons/</link><pubDate>Thu, 24 May 2012 11:02:19 -0300</pubDate><guid>https://scholion.thluiz.com/notes/solid-code-for-solid-reasons/</guid><description>The post argues that good code should be written for maintainability, with testability as a secondary benefit. It connects SOLID, bounded contexts, and anti-corruption layers to TDD and criticizes using moles or shims to justify weak design.</description></item></channel></rss>