<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Data-Migration on Brian Faust</title><link>https://wimdy.works/tags/data-migration/</link><description>Recent content in Data-Migration on Brian Faust</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 01 Jan 0001 00:00:00 +0000</lastBuildDate><atom:link href="https://wimdy.works/tags/data-migration/rss.xml" rel="self" type="application/rss+xml"/><item><title>Stored Data Is a Caller You Cannot Find with Code Search</title><link>https://wimdy.works/thoughts/stored-data-is-a-caller-you-cannot-find-with-code-search/</link><pubDate>Sun, 01 Dec 2019 00:00:00 +0000</pubDate><guid>https://wimdy.works/thoughts/stored-data-is-a-caller-you-cannot-find-with-code-search/</guid><description>&lt;p&gt;An enum migration looked mechanical. A package-backed value object became a
native PHP backed enum. The domain concept stayed the same, the new cases were
easy to search, and current code wrote the canonical values. It was exactly the
kind of refactor that looks finished after a clean source search.&lt;/p&gt;
&lt;p&gt;Then an older row loaded a lowercase value. The native enum expected the same
word with different casing and rejected it during hydration.&lt;/p&gt;</description></item></channel></rss>