<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pattern on Machine-Cycle</title>
    <link>https://machine-cycle.pages.dev/en/tags/pattern/</link>
    <description>Recent content in Pattern on Machine-Cycle</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Wed, 29 Jul 2020 10:00:00 +0200</lastBuildDate><atom:link href="https://machine-cycle.pages.dev/en/tags/pattern/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Golden Master Pattern: don’t fear the legacy code!</title>
      <link>https://machine-cycle.pages.dev/en/posts/golden_master/</link>
      <pubDate>Wed, 29 Jul 2020 10:00:00 +0200</pubDate>
      
      <guid>https://machine-cycle.pages.dev/en/posts/golden_master/</guid>
      <description>Let’s see together how to modify legacy code ensuring it works thanks to the Golden Master Pattern Anyone who works in the software development world will have had the need to add features on the legacy code, perhaps inherited from the previous team, and on which you need to make an urgent fix.
Many definitions of legacy code can be found in literature, the one that I prefer is: “By Legacy code, we mean the profitable code that we feel afraid to change”.</description>
    </item>
    
  </channel>
</rss>
