<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cloudflare-R2 on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</title>
    <link>https://ronaldbradford.com/tags/cloudflare-r2/</link>
    <description>Recent content in Cloudflare-R2 on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 17 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ronaldbradford.com/tags/cloudflare-r2/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Curating DuckDB Datasets Leveraging AI</title>
      <link>https://ronaldbradford.com/blog/2026-08-17-curating-duckdb-datasets-leveraging-ai/</link>
      <pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/2026-08-17-curating-duckdb-datasets-leveraging-ai/</guid>
      <description>In Curated MySQL Data Sets for Realistic Testing I described datasets assembled the manual way — download, schema, load, validate, document — over hours or days per source. This post is the follow-up I promised: what changes when AI assists the same workflow, using DuckDB as the target engine and GeoNames as the first example.</description>
    </item>
  </channel>
</rss>
