<?xml version="1.0" encoding="UTF-8" ?>
  <rss version="2.0">
    <channel>
        <title>ProCheck Engineering Blog</title>
        <link>https://portfolio-blog-starter.vercel.app</link>
        <description>Engineering blog for ProCheck — taking the factory to the cloud.</description>
        <item>
          <title>Our First Archival at Scale: Anatomy of a 30-Minute Incident</title>
          <link>https://portfolio-blog-starter.vercel.app/blog/archival-pipeline-incident-postmortem</link>
          <description>As Procheck has grown, so has the volume of sensor and OEE data sitting in our primary database — enough that we recently ran our first large-scale archival job to move old data into cold storage. That job failed partway through and left cursors hanging behind it, triggering our first real incident of this kind. Here's the full timeline, what we did, and what changed as a result.</description>
          <pubDate>Wed, 26 Aug 2026 00:00:00 GMT</pubDate>
        </item>
<item>
          <title>A Phased Migration Toward a Faster, More Reliable OEE Platform</title>
          <link>https://portfolio-blog-starter.vercel.app/blog/rebuilding-our-oee-backend-infrastructure</link>
          <description>Procheck's backend is getting a ground-up rebuild. We're rolling out a new OEE backend in phases — validating it against live production data before it takes over write traffic — while scaling our read replica, adding better indexing and caching, and consolidating to a single region for speed and reliability. Alongside it, our frontend is getting a full modernization, and we're finally giving our codebase the test coverage it always needed. Here's how we're doing it without breaking things along the way.</description>
          <pubDate>Tue, 18 Aug 2026 00:00:00 GMT</pubDate>
        </item>
<item>
          <title>Tracking and debugging millions of IoT Packets at scale</title>
          <link>https://portfolio-blog-starter.vercel.app/blog/tracking-and-debugging-millions-of-iot-packets-at-scale</link>
          <description>Debugging a system that ingests hundreds of thousands of sensor packets per shift is nearly impossible without the right visibility. We built an internal dev dashboard that plots sensor heartbeats and packet counts over time, automatically converting between UTC (how we store data) and local time (how our team thinks about a shift) — turning hours of log-diving into a five-second glance at a graph.</description>
          <pubDate>Tue, 18 Aug 2026 00:00:00 GMT</pubDate>
        </item>
<item>
          <title>Eliminating a Round-Trip at Build Time</title>
          <link>https://portfolio-blog-starter.vercel.app/blog/bundling-plant-config</link>
          <description>A configuration fetch that ran on every page load was pure overhead. Moving it to build time cut load latency and removed a failure point.</description>
          <pubDate>Tue, 04 Aug 2026 00:00:00 GMT</pubDate>
        </item>
<item>
          <title>Reworking a Dashboard Page Without Breaking the Data</title>
          <link>https://portfolio-blog-starter.vercel.app/blog/line-performance-monitor-rework</link>
          <description>A layout rework looked clean in testing. Three regressions made it through. Here is what they were and what they taught us.</description>
          <pubDate>Tue, 04 Aug 2026 00:00:00 GMT</pubDate>
        </item>
<item>
          <title>UI Refresh 2026: What We Shipped and What We Learned</title>
          <link>https://portfolio-blog-starter.vercel.app/blog/ui-refresh-2026-overview</link>
          <description>A tour of the Q3 2026 frontend overhaul — skeleton loading, date filtering, error boundaries, and what the operators actually noticed.</description>
          <pubDate>Tue, 04 Aug 2026 00:00:00 GMT</pubDate>
        </item>
<item>
          <title>Six Years Later: What We Learned Shipping a UI Update to Operators</title>
          <link>https://portfolio-blog-starter.vercel.app/blog/ui-refresh-six-year-gap</link>
          <description>We shipped a major UI refresh after six years. The engineering was solid. The rollout was over in six hours.</description>
          <pubDate>Tue, 04 Aug 2026 00:00:00 GMT</pubDate>
        </item>
    </channel>
  </rss>