<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Seams on Scholion</title><link>https://scholion.thluiz.com/tags/seams/</link><description>Recent content in Seams on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Mon, 16 Nov 2026 15:09:12 +0000</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/seams/index.xml" rel="self" type="application/rss+xml"/><item><title>The key points of Working Effectively with Legacy Code - Change Messy Software Without Breaking It</title><link>https://scholion.thluiz.com/notes/the-key-points-of-working-effectively-with-legacy-code/</link><pubDate>Sun, 05 Jul 2020 14:11:20 +0000</pubDate><guid>https://scholion.thluiz.com/notes/the-key-points-of-working-effectively-with-legacy-code/</guid><description>The book argues that the safest way to change legacy code is to add fast automated tests first, then refactor. It introduces seams, characterization tests, and Sprout/Wrap techniques for risky code.</description></item></channel></rss>