https://www.renatoteixeira.com/Recent content on RenatoTeixeira.comHugoenThu, 23 Apr 2026 00:00:00 +0000https://www.renatoteixeira.com/posts/modernization-not-dispute/Thu, 23 Apr 2026 00:00:00 +0000https://www.renatoteixeira.com/posts/modernization-not-dispute/<p>There is a recurring tendency to treat legacy as a historical mistake to be corrected. As if identifying a more current technology, designing a more elegant architecture, and starting a replacement journey were enough to solve the problem once and for all.</p> <p>But reality rarely organizes itself that way.</p> <p><strong>Legacy systems</strong> do not persist simply because organizations resist change. They persist because, at some point, they were successful in sustaining critical operations, absorbing real business complexity, and accommodating, over time, decisions, exceptions, adaptations, and trade-offs that can hardly be captured in a clean architectural diagram.</p>https://www.renatoteixeira.com/posts/legacy-does-no-happen-by-accident/Tue, 14 Apr 2026 00:00:00 +0000https://www.renatoteixeira.com/posts/legacy-does-no-happen-by-accident/<p>Legacy does not emerge as an isolated failure, nor as a simple consequence of age. In most important systems, it is the result of continuous adaptation under real pressures: new requirements, operational constraints, accumulated decisions, and the constant need to remain useful in a changing environment.</p> <p>That is why <strong>Meir Lehman’s (1980)</strong> article remains so valuable to me. It does not treat software as a static artifact, but as something shaped by ongoing evolution. And for that reason, I believe it deserves to be much better known by those who work in the day-to-day practice of IT.</p>https://www.renatoteixeira.com/contact/Mon, 01 Jan 0001 00:00:00 +0000https://www.renatoteixeira.com/contact/<p>Follow me, @johndoe.</p>https://www.renatoteixeira.com/projects/Mon, 01 Jan 0001 00:00:00 +0000https://www.renatoteixeira.com/projects/<p>Nothing to see here&hellip; Move along!</p>