<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Data on Vitor Pontual | The VeePee Hub</title>
    <link>https://vitorpontual.com/tags/data/</link>
    <description>Recent content in Data on Vitor Pontual | The VeePee Hub</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 29 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://vitorpontual.com/tags/data/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>VeePeenini, Part 3: Launch and the Long Tail of Data</title>
      <link>https://vitorpontual.com/posts/veepeenini-3-launch-and-the-long-tail/</link>
      <pubDate>Fri, 29 May 2026 00:00:00 +0000</pubDate>
      <guid>https://vitorpontual.com/posts/veepeenini-3-launch-and-the-long-tail/</guid>
      <description>&lt;p&gt;The day after launch, one of my friends sent me a message: a group on the bracket was showing the wrong teams. Not a crash, not an error page. Just quietly, confidently wrong. This is exactly the kind of bug you only catch once real people are looking, because they know the tournament better than your test data does.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-bug-that-was-really-two-files-arguing&#34;&gt;The bug that was really two files arguing&lt;/h2&gt;&#xA;&lt;p&gt;The group letters were wrong on the bracket but right everywhere the actual fixtures were involved. When I dug in with Claude, the cause was almost funny: two different files in the codebase each held their own hardcoded copy of which team is in which group, and over a week of changes they had drifted apart. Nine of the twelve groups had at least one wrong assignment in one of the files. The database, the actual source of truth, had been correct the whole time.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
