<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
<title>Edward Plata</title>
<link>https://edwardplata.com</link>
<description>Edward Plata is a data engineer in New York building lakehouses, streaming pipelines and platforms other engineers can safely build on.</description>
<language>en</language>
<atom:link href="https://edwardplata.com/rss.xml" rel="self" type="application/rss+xml"/>
    <item><title>What 30 days of data engineering threads say: a research log</title><link>https://edwardplata.com/blog/what-30-days-of-data-engineering-threads-say</link><guid>https://edwardplata.com/blog/what-30-days-of-data-engineering-threads-say</guid><pubDate>Sun, 8 Nov 2026 12:00:00 +0000</pubDate><description>I ran a research script over 30 days of Reddit, Hacker News, GitHub and dev.to posts about data engineering. These are the five arguments I found, what the evidence can carry, and what I will test myself.</description></item>
    <item><title>Every number on my resume has to survive one follow-up question</title><link>https://edwardplata.com/blog/every-number-on-my-resume-has-to-survive-one-question</link><guid>https://edwardplata.com/blog/every-number-on-my-resume-has-to-survive-one-question</guid><pubDate>Thu, 29 Oct 2026 12:00:00 +0000</pubDate><description>I audited my resume the way I audit a pipeline: every claim is a row, every number needs provenance, and a build check decides what is allowed on the public copy.</description></item>
    <item><title>A resume review checklist for data engineers</title><link>https://edwardplata.com/blog/a-resume-review-checklist-for-data-engineers</link><guid>https://edwardplata.com/blog/a-resume-review-checklist-for-data-engineers</guid><pubDate>Wed, 28 Oct 2026 12:00:00 +0000</pubDate><description>The checks I now run on any data engineering resume, mine included: the six-second read, the X-Y-Z bullet, scope over tools, one claim per number, and what an ATS really does.</description></item>
    <item><title>What 73 autonomous experiments taught me</title><link>https://edwardplata.com/blog/what-73-autonomous-experiments-taught-me</link><guid>https://edwardplata.com/blog/what-73-autonomous-experiments-taught-me</guid><pubDate>Tue, 27 Oct 2026 12:00:00 +0000</pubDate><description>An unattended research loop on Numerai ran 73 experiments and kept almost none. Why that was mostly the loop working, and the places it quietly wasn&#39;t.</description></item>
    <item><title>From a rented k3s node to a NAS in the closet</title><link>https://edwardplata.com/blog/from-a-rented-k3s-node-to-a-nas-in-the-closet</link><guid>https://edwardplata.com/blog/from-a-rented-k3s-node-to-a-nas-in-the-closet</guid><pubDate>Tue, 20 Oct 2026 12:00:00 +0000</pubDate><description>What running my own media, photos and passwords taught me: healthy is not working, a check that cannot fail is not a check, and a backup is a restore.</description></item>
    <item><title>A silver layer and an agent over NYC Open Data</title><link>https://edwardplata.com/blog/a-silver-layer-and-an-agent-over-nyc-open-data</link><guid>https://edwardplata.com/blog/a-silver-layer-and-an-agent-over-nyc-open-data</guid><pubDate>Tue, 13 Oct 2026 12:00:00 +0000</pubDate><description>Why my silver layer holds no source rows, how 280 bytes from 21.9M rows changed the design, and what it took to make a free-tier agent answer correctly.</description></item>
    <item><title>I treated my job search as a data warehouse</title><link>https://edwardplata.com/blog/i-treated-my-job-search-as-a-data-warehouse</link><guid>https://edwardplata.com/blog/i-treated-my-job-search-as-a-data-warehouse</guid><pubDate>Tue, 6 Oct 2026 12:00:00 +0000</pubDate><description>Raw JSON in, enforced contracts in the middle, an app on top. What building a personal warehouse for a job search taught me about source agnosticism and data ownership.</description></item>
  </channel>
</rss>
