<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Python on bradleycarey.com</title>
    <link>https://bradleycarey.com/tags/python/</link>
    <description>Recent content in Python on bradleycarey.com</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 13 Mar 2026 19:46:37 -0400</lastBuildDate>
    <atom:link href="https://bradleycarey.com/tags/python/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>I Built a Full CLI for a Legacy Web App in One Afternoon (with AI)</title>
      <link>https://bradleycarey.com/posts/building-a-cli-for-a-legacy-app-with-ai/</link>
      <pubDate>Fri, 13 Mar 2026 12:00:00 -0400</pubDate>
      <guid>https://bradleycarey.com/posts/building-a-cli-for-a-legacy-app-with-ai/</guid>
      <description>&lt;p&gt;Our platform has been around for nearly two decades. The backend is a sprawl of three separate HTTP services: a legacy REST API (v1), a newer REST API (v2), and an Elasticsearch-backed search service. They share a JWT token but have different base URLs, different conventions, and different quirks. There&amp;rsquo;s no unified CLI. If you want to poke at the API, you open Swagger, copy a Bearer token, and start curling.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Proof Of Work: A Strength Training Dashboard</title>
      <link>https://bradleycarey.com/posts/strength-training-dashboard/</link>
      <pubDate>Sat, 28 Feb 2026 12:00:00 -0500</pubDate>
      <guid>https://bradleycarey.com/posts/strength-training-dashboard/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve been tracking my workouts with &lt;a href=&#34;https://play.google.com/store/apps/details?id=com.maxworkoutcoach.workouttrainer.workouttrainer&amp;amp;hl=en_US&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;the same Android app&lt;/a&gt; for almost 7 years. Nearly a thousand workouts, 59,000 reps, 6.8 million pounds of volume. The app does its job, but the data just sits there. I wanted to actually see it.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;&lt;a href=&#34;https://bradleycarey.com/dashboard/&#34; &gt;Check out the dashboard&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-problem&#34;&gt;&#xA;  The Problem&#xA;  &lt;a class=&#34;heading-link&#34; href=&#34;#the-problem&#34;&gt;&#xA;    &lt;i class=&#34;fa-solid fa-link&#34; aria-hidden=&#34;true&#34; title=&#34;Link to heading&#34;&gt;&lt;/i&gt;&#xA;    &lt;span class=&#34;sr-only&#34;&gt;Link to heading&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Workout apps are great at recording sets and reps. They&amp;rsquo;re terrible at showing you the big picture. I wanted to answer questions like: how has my squat progressed over 6 years? When was my best training year? How consistent am I really? What does 6.8 million pounds even look like?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
