<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Fitness on bradleycarey.com</title>
    <link>https://bradleycarey.com/categories/fitness/</link>
    <description>Recent content in Fitness on bradleycarey.com</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 22 Mar 2026 20:10:53 -0400</lastBuildDate>
    <atom:link href="https://bradleycarey.com/categories/fitness/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How I Hit a 315 lb Bench Press</title>
      <link>https://bradleycarey.com/posts/how-i-hit-a-315-lb-bench-press/</link>
      <pubDate>Sun, 22 Mar 2026 11:53:59 -0400</pubDate>
      <guid>https://bradleycarey.com/posts/how-i-hit-a-315-lb-bench-press/</guid>
      <description>&lt;p&gt;The projected max got there before the actual lift did. I hit 275 for 5 reps on December 9, 2022, which projects to a 320 lb estimated one-rep max via the &lt;a href=&#34;https://en.wikipedia.org/wiki/One-repetition_maximum&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Epley formula&lt;/a&gt;. I did load 320 on the bar shortly after just to say I&amp;rsquo;d actually touched it. But the data already called it. That took almost four years of training, two years of spinning my wheels, and one program that finally made the difference.&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>
    <item>
      <title>Strength Training Is a Force Multiplier for Knowledge Workers</title>
      <link>https://bradleycarey.com/posts/strength-training-as-a-knowledge-worker/</link>
      <pubDate>Thu, 01 Jan 2026 15:19:44 -0400</pubDate>
      <guid>https://bradleycarey.com/posts/strength-training-as-a-knowledge-worker/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&amp;ldquo;It is a shame for a man to grow old without seeing the beauty and strength of which his body is capable.&amp;rdquo;&#xA;— Socrates&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;Most knowledge workers treat their bodies like a laptop they never charge properly. Good enough to get through the day, running at 60%, wondering why they&amp;rsquo;re tired by 3pm.&lt;/p&gt;&#xA;&lt;p&gt;Strength training fixes this. Not walking, not yoga, not &amp;ldquo;being more active.&amp;rdquo; Specifically lifting weights, progressively, a few times a week. It is a systems upgrade. Improves throughput (energy), stability (stress), error rates (focus), and uptime (health) across the entire human stack. Here&amp;rsquo;s why.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
