<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Beyond the Formatter: How a Simple JSON Task Taught Me the Weight of Global Data Integrity]]></title><description><![CDATA[Beyond the Formatter: How a Simple JSON Task Taught Me the Weight of Global Data Integrity]]></description><link>https://shehrbanoali.hashnode.dev</link><image><url>https://cdn.hashnode.com/uploads/logos/69c4efaf10e664c5da8226b4/3842d76b-172f-45a6-8c20-f8f00434a713.png</url><title>Beyond the Formatter: How a Simple JSON Task Taught Me the Weight of Global Data Integrity</title><link>https://shehrbanoali.hashnode.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Mon, 16 Nov 2026 18:59:04 GMT</lastBuildDate><atom:link href="https://shehrbanoali.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Beyond the Formatter: How a Simple JSON Task Taught Me the Weight of Global Data Integrity]]></title><description><![CDATA[My Experience:]]></description><link>https://shehrbanoali.hashnode.dev/beyond-the-formatter-how-a-simple-json-task-taught-me-the-weight-of-global-data-integrity</link><guid isPermaLink="true">https://shehrbanoali.hashnode.dev/beyond-the-formatter-how-a-simple-json-task-taught-me-the-weight-of-global-data-integrity</guid><category><![CDATA[outreachy internship 2026]]></category><category><![CDATA[Wikipedia]]></category><category><![CDATA[wikimedia]]></category><category><![CDATA[lusophone]]></category><category><![CDATA[JavaScript]]></category><category><![CDATA[json]]></category><dc:creator><![CDATA[Shehrbano Ali]]></dc:creator><pubDate>Sun, 05 Apr 2026 15:23:18 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/69c4efaf10e664c5da8226b4/dbc8954e-2699-419e-a775-f064cb1f8417.jpg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>When I first looked at this task, it seemed like a very quick job. I expected to finish it in one sitting without any major issues. The goal was simple: use a bit of <strong>JavaScript</strong> to take some <strong>JSON data</strong> and print it in a human legible format. Nothing about it looked complex. Nothing hinted that it would demand more than just a <code>forEach</code> loop and a bit of <strong>DOM manipulation</strong>.  </p>
<p>So I simply opened VS Code, looked at the JSON data, and began to write. For a moment, everything seemed to go exactly as expected. The logic worked, the dates appeared on the screen, and technically, I had already completed the core requirement.  </p>
<p>But something felt odd.  </p>
<p>As I looked at the rendered results, I noticed a discrepancy. The raw data said <strong>André Baniwa’s</strong> page was created on <strong>September 13th</strong>. But when I checked the example output in the instructions, it said <strong>September 12th.</strong>  </p>
<p>It was a one digit difference. A single day. I could have ignored it. I could have assumed it was a typo in the manual and submitted my correct version. That would have been enough.  </p>
<p>But I paused.  </p>
<p>Because I realized I didn’t actually understand why the gap existed and that difference started to bother me.  </p>
<p>So instead of moving forward, I went back.  </p>
<p>I began to slow everything down. I began to investigate how JavaScript interprets <strong>ISO dates</strong>. I learned that new <code>Date(2021-09-13)</code> doesn't just mean a date, it means a specific moment in <strong>UTC time</strong>. And for a developer in a different timezone, that moment shifts.  </p>
<p>The system wasn't broken; it was behaving exactly as programmed, but it was failing the user. That realization shifted how I saw the entire task.  </p>
<p>It was no longer about formatting strings.  </p>
<p>It was about understanding how global data remains true across borders.  </p>
<p>That shift changed my approach completely. I implemented the <code>T00:00:00</code> fix, ensuring that regardless of where a Wikimedia editor is standing, be it in <em>Pakistan, Brazil, or the US</em>, the history of that page remains accurate.  </p>
<p>But then, I looked even further.  </p>
<p>I looked at the project I was applying for: <strong>Addressing the Lusophone technological wishlist</strong>. I realized that the core of that project wasn't just about writing code; it was about solving community pain points. One of those points was <a href="https://meta.wikimedia.org/wiki/Lista_de_desejos_tecnol%C3%B3gicos_da_lusofonia/2025/Propostas/Verificar_automaticamente_uma_refer%C3%AAncia_duplicada">Wishlist Proposal #3: Duplicate Reference Detection</a>.  </p>
<p>I asked myself: If I can normalize a date to prevent a shift, can I normalize a <strong>URL</strong> to prevent a duplicate?  </p>
<p>This wasn't part of the original instructions, but it felt necessary. I designed a small experiment within my task, a <strong>Wiki Reference Guard</strong>. I applied the same principles of <em>string manipulation</em> and <em>data validation</em> to create a prototype that could strip protocols and prefixes, identifying that two different looking links were actually the same source.  </p>
<p>At that point, I stopped thinking like someone trying to complete a microtask and started thinking like someone contributing to an ecosystem. I found myself asking deeper questions. How does a small logic error in a script impact a contributor's trust in the platform? How can simple code prevent the clutter that slows down the world's largest encyclopedia?  </p>
<p>Of course, the journey wasn't perfect. I struggled with GitHub Pages deployments, I wrestled with Markdown formatting, and I had to iterate on my <strong>README</strong> multiple times to ensure it was mentorship ready.  </p>
<p>Each of those moments could have been frustrating, but they ended up being the most valuable parts of the process. They forced me to engage more deeply, to read documentation carefully, and to understand the industry standard instead of guessing. Instead of skipping past errors, I documented them, broke them down, and learned from them.  </p>
<p>Over time, something became very clear.  </p>
<p>This entire process, what many call the contribution period, is not just a trial. It is a transformation. It is the stage where you stop being an applicant and start becoming a collaborator. If your foundation is built on just finishing tasks, your contributions will be fragile. But if you build on a foundation of understanding, your work becomes an asset to the community.  </p>
<p>Now looking back I wonder how a simple instruction to format a <strong>JSON object</strong> turned into a deep dive into <em>timezone logic</em> and <em>community wishlist proposals</em>. What seemed like a small task revealed an entire layer of technical empathy that usually goes unnoticed.  </p>
<p>If I had rushed through it, I would have missed all of that.  </p>
<p>And I think that’s the real lesson I’m taking away from this experience. Sometimes, the most valuable part of the work is hidden in the step that feels the most routine. The difference comes down to whether you choose to just finish it, or to actually understand it.  </p>
<p>This was my first deep experience working through a <strong>Wikimedia task</strong> and it taught me that in open source, no detail is too small to care about. I’m ready to see what the next challenge brings.  </p>
<p><em>Thank you! :)<br />Shehrbano Ali</em></p>
]]></content:encoded></item></channel></rss>