<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Chad Dyar</title>
    <description>The latest articles on DEV Community by Chad Dyar (@chadtdyar).</description>
    <link>https://dev.to/chadtdyar</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3811599%2F0adb0b4b-5659-4c7c-8f09-49347539478f.jpg</url>
      <title>DEV Community: Chad Dyar</title>
      <link>https://dev.to/chadtdyar</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/chadtdyar"/>
    <language>en</language>
    <item>
      <title>The Sales Call Version of "Micro Workouts"</title>
      <dc:creator>Chad Dyar</dc:creator>
      <pubDate>Tue, 28 Jul 2026 22:11:13 +0000</pubDate>
      <link>https://dev.to/chadtdyar/the-sales-call-version-of-micro-workouts-3kpe</link>
      <guid>https://dev.to/chadtdyar/the-sales-call-version-of-micro-workouts-3kpe</guid>
      <description>&lt;p&gt;My trainer told me last week that she's seeing better results from clients doing three ten-minute sessions throughout the day than grinding through one brutal hour at the gym. Something about consistency mattering more than intensity. Cortisol, recovery, sustainability, the usual science.&lt;/p&gt;

&lt;p&gt;She wasn't trying to make a business analogy. But I heard one anyway.&lt;/p&gt;

&lt;p&gt;I've been tracking my prospect conversations for the past quarter, and the pattern is obvious now. The deals that close aren't coming from the marathon discovery calls where I try to unpack their entire business model in sixty minutes. They're coming from the quick fifteen-minute check-ins where we tackle one specific objection or walk through one part of the pricing model.&lt;/p&gt;

&lt;p&gt;The micro workout principle applies to sales execution in ways that feel almost embarrassingly obvious once you see it. Your prospect's attention span works like muscle recovery. You can't force understanding or trust into a single exhausting session. You build both through repeated, focused contact. Three short calls over two weeks will always beat one comprehensive call that leaves everyone drained.&lt;/p&gt;

&lt;p&gt;The practical shift is smaller than it sounds. I started blocking my calendar differently. Instead of holding slots for hour-long discovery calls, I book three twenty-minute conversations spread across the week. First call covers their current process. Second call explores one pain point we identified. Third call introduces how we'd solve that specific problem.&lt;/p&gt;

&lt;p&gt;The conversion rate difference showed up in under a month. Not because my pitch improved, but because prospects actually remembered our previous conversations. They'd done the thinking between calls. They'd talked to their team. They came back with real questions instead of polite objections.&lt;/p&gt;

&lt;p&gt;This maps directly to what I cover in Think On Your Feet, Land On Your Numbers, particularly around call preparation and question sequencing. The temptation in sales is always to pack everything into one interaction. More features, more case studies, more proof points. But that's training for exhaustion, not results.&lt;/p&gt;

&lt;p&gt;Micro workouts work because they respect recovery time. Micro calls work because they respect processing time. Both require you to trust the compound effect of showing up consistently instead of trying to earn everything in one session.&lt;/p&gt;

&lt;p&gt;Your prospects aren't avoiding your follow-up because they're not interested. They're avoiding it because the last call left them tired.&lt;/p&gt;

</description>
      <category>buildinpublic</category>
      <category>productivity</category>
    </item>
    <item>
      <title>The newest Presswright title is live on Amazon: Large Print Word Search for Nostalgic Minds: 45 Cherished Themes, Vol...</title>
      <dc:creator>Chad Dyar</dc:creator>
      <pubDate>Fri, 24 Jul 2026 22:11:09 +0000</pubDate>
      <link>https://dev.to/chadtdyar/the-newest-presswright-title-is-live-on-amazon-large-print-word-search-for-nostalgic-minds-45-5475</link>
      <guid>https://dev.to/chadtdyar/the-newest-presswright-title-is-live-on-amazon-large-print-word-search-for-nostalgic-minds-45-5475</guid>
      <description>&lt;p&gt;The newest Presswright title is live on Amazon: Large Print Word Search for Nostalgic Minds: 45 Cherished Themes, Volume 4. It is a large print word search book for seniors, and the book is ordinary on purpose. The pipeline is the project.&lt;/p&gt;

&lt;p&gt;Presswright is a small agent system that takes a puzzle book from theme list to print-ready interior: one agent drafts themed word lists, one validates every grid for solvability and overlap rules, one typesets the large print interior, and a final gate rejects anything that fails a checklist before the PDF ever reaches KDP. The lesson so far: generation was the easy half. The real work lives in the validation gates. When a grid fails, the pipeline logs the defect and regenerates instead of shipping a broken puzzle to a paying reader.&lt;/p&gt;

&lt;p&gt;The book that came out the other end is here: &lt;a href="https://www.amazon.com/dp/B0H9G4PMW2" rel="noopener noreferrer"&gt;https://www.amazon.com/dp/B0H9G4PMW2&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Shipping a paperback with an agent pipeline</title>
      <dc:creator>Chad Dyar</dc:creator>
      <pubDate>Fri, 24 Jul 2026 21:00:02 +0000</pubDate>
      <link>https://dev.to/chadtdyar/shipping-a-paperback-with-an-agent-pipeline-1mj4</link>
      <guid>https://dev.to/chadtdyar/shipping-a-paperback-with-an-agent-pipeline-1mj4</guid>
      <description>&lt;p&gt;The newest Presswright title is live on Amazon: Large Print Word Search for Nostalgic Minds: 45 Cherished Themes, Volume 4. It is a large print word search book for seniors, and the book is ordinary on purpose. The pipeline is the project. Presswright is a small agent system that takes a puzzle book from theme list to print-ready interior: one agent drafts themed word lists, one validates every grid for solvability and overlap rules, one typesets the large print interior, and a final gate rejects anything that fails a checklist before the PDF ever reaches KDP. The lesson so far: generation was the easy half. The real work lives in the validation gates. When a grid fails, the pipeline logs the defect and regenerates instead of shipping a broken puzzle to a paying reader.&lt;/p&gt;

</description>
      <category>pethealth</category>
      <category>dogowners</category>
      <category>pawformance</category>
      <category>buildinpublic</category>
    </item>
    <item>
      <title>Performance Amplified</title>
      <dc:creator>Chad Dyar</dc:creator>
      <pubDate>Thu, 23 Jul 2026 14:00:03 +0000</pubDate>
      <link>https://dev.to/chadtdyar/performance-amplified-4lfn</link>
      <guid>https://dev.to/chadtdyar/performance-amplified-4lfn</guid>
      <description>&lt;h1&gt;
  
  
  Performance Amplified
&lt;/h1&gt;

&lt;p&gt;This one came from years of hands-on work, not a weekend brainstorm. If you want practical frameworks you can use tomorrow, not inspirational fluff, this is where to start.&lt;/p&gt;

&lt;p&gt;Grab it here: &lt;a href="https://www.chadtdyar.com/books/performance-amplified" rel="noopener noreferrer"&gt;https://www.chadtdyar.com/books/performance-amplified&lt;/a&gt;&lt;/p&gt;

</description>
      <category>pethealth</category>
      <category>dogowners</category>
      <category>pawformance</category>
      <category>buildinpublic</category>
    </item>
    <item>
      <title>The Gospel Trilogy</title>
      <dc:creator>Chad Dyar</dc:creator>
      <pubDate>Thu, 23 Jul 2026 14:00:02 +0000</pubDate>
      <link>https://dev.to/chadtdyar/the-gospel-trilogy-12e</link>
      <guid>https://dev.to/chadtdyar/the-gospel-trilogy-12e</guid>
      <description>&lt;h1&gt;
  
  
  The Gospel Trilogy
&lt;/h1&gt;

&lt;p&gt;This one came from years of hands-on work, not a weekend brainstorm. If you want practical frameworks you can use tomorrow, not inspirational fluff, this is where to start.&lt;/p&gt;

&lt;p&gt;Grab it here: &lt;a href="https://www.chadtdyar.com/books/the-gospel-trilogy" rel="noopener noreferrer"&gt;https://www.chadtdyar.com/books/the-gospel-trilogy&lt;/a&gt;&lt;/p&gt;

</description>
      <category>pethealth</category>
      <category>dogowners</category>
      <category>pawformance</category>
      <category>buildinpublic</category>
    </item>
    <item>
      <title>The Nightmare Trilogy</title>
      <dc:creator>Chad Dyar</dc:creator>
      <pubDate>Wed, 22 Jul 2026 14:00:03 +0000</pubDate>
      <link>https://dev.to/chadtdyar/the-nightmare-trilogy-10ch</link>
      <guid>https://dev.to/chadtdyar/the-nightmare-trilogy-10ch</guid>
      <description>&lt;h1&gt;
  
  
  The Nightmare Trilogy
&lt;/h1&gt;

&lt;p&gt;This one came from years of hands-on work, not a weekend brainstorm. If you want practical frameworks you can use tomorrow, not inspirational fluff, this is where to start.&lt;/p&gt;

&lt;p&gt;Grab it here: &lt;a href="https://www.chadtdyar.com/books/the-nightmare-trilogy" rel="noopener noreferrer"&gt;https://www.chadtdyar.com/books/the-nightmare-trilogy&lt;/a&gt;&lt;/p&gt;

</description>
      <category>pethealth</category>
      <category>dogowners</category>
      <category>pawformance</category>
      <category>buildinpublic</category>
    </item>
    <item>
      <title>The Nightmare Trilogy</title>
      <dc:creator>Chad Dyar</dc:creator>
      <pubDate>Wed, 22 Jul 2026 13:22:25 +0000</pubDate>
      <link>https://dev.to/chadtdyar/the-nightmare-trilogy-31jp</link>
      <guid>https://dev.to/chadtdyar/the-nightmare-trilogy-31jp</guid>
      <description>&lt;h1&gt;
  
  
  The Nightmare Trilogy
&lt;/h1&gt;

&lt;p&gt;This one came from years of hands-on work, not a weekend brainstorm. If you want practical frameworks you can use tomorrow, not inspirational fluff, this is where to start.&lt;/p&gt;

&lt;p&gt;Grab it here: &lt;a href="https://www.chadtdyar.com/books/the-nightmare-trilogy" rel="noopener noreferrer"&gt;https://www.chadtdyar.com/books/the-nightmare-trilogy&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>The Sparkle, the Snuggle, and the Song</title>
      <dc:creator>Chad Dyar</dc:creator>
      <pubDate>Wed, 22 Jul 2026 13:22:24 +0000</pubDate>
      <link>https://dev.to/chadtdyar/the-sparkle-the-snuggle-and-the-song-86h</link>
      <guid>https://dev.to/chadtdyar/the-sparkle-the-snuggle-and-the-song-86h</guid>
      <description>&lt;h1&gt;
  
  
  The Sparkle, the Snuggle, and the Song
&lt;/h1&gt;

&lt;p&gt;This one came from years of hands-on work, not a weekend brainstorm. If you want practical frameworks you can use tomorrow, not inspirational fluff, this is where to start.&lt;/p&gt;

&lt;p&gt;Grab it here: &lt;a href="https://www.chadtdyar.com/books/the-sparkle-snuggle-song" rel="noopener noreferrer"&gt;https://www.chadtdyar.com/books/the-sparkle-snuggle-song&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Humbled to Announce</title>
      <dc:creator>Chad Dyar</dc:creator>
      <pubDate>Tue, 21 Jul 2026 15:50:20 +0000</pubDate>
      <link>https://dev.to/chadtdyar/humbled-to-announce-1e09</link>
      <guid>https://dev.to/chadtdyar/humbled-to-announce-1e09</guid>
      <description>&lt;h1&gt;
  
  
  Humbled to Announce
&lt;/h1&gt;

&lt;p&gt;This one came from years of hands-on work, not a weekend brainstorm. If you want practical frameworks you can use tomorrow, not inspirational fluff, this is where to start.&lt;/p&gt;

&lt;p&gt;Grab it here: &lt;a href="https://www.chadtdyar.com/books/humbled-to-announce" rel="noopener noreferrer"&gt;https://www.chadtdyar.com/books/humbled-to-announce&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Performance Whisperer</title>
      <dc:creator>Chad Dyar</dc:creator>
      <pubDate>Tue, 21 Jul 2026 15:50:17 +0000</pubDate>
      <link>https://dev.to/chadtdyar/performance-whisperer-478</link>
      <guid>https://dev.to/chadtdyar/performance-whisperer-478</guid>
      <description>&lt;h1&gt;
  
  
  Performance Whisperer
&lt;/h1&gt;

&lt;p&gt;This one came from years of hands-on work, not a weekend brainstorm. If you want practical frameworks you can use tomorrow, not inspirational fluff, this is where to start.&lt;/p&gt;

&lt;p&gt;Grab it here: &lt;a href="https://www.chadtdyar.com/books/performance-whisperer" rel="noopener noreferrer"&gt;https://www.chadtdyar.com/books/performance-whisperer&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Every gym friend I have said some version of the same sentence while I was building Momentum: "It's not like college anymore. We</title>
      <dc:creator>Chad Dyar</dc:creator>
      <pubDate>Tue, 21 Jul 2026 14:50:16 +0000</pubDate>
      <link>https://dev.to/chadtdyar/every-gym-friend-i-have-said-some-version-of-the-same-sentence-while-i-was-building-momentum-its-1m64</link>
      <guid>https://dev.to/chadtdyar/every-gym-friend-i-have-said-some-version-of-the-same-sentence-while-i-was-building-momentum-its-1m64</guid>
      <description>&lt;p&gt;Every gym friend I have said some version of the same sentence while I was building Momentum: "It's not like college anymore. We know what to do. We just need to actually show up."&lt;/p&gt;

&lt;p&gt;I have worked out since I was 15. At 50 I am busier and more tired, and the thing that changed was never motivation or knowledge. I can write you a decent training plan from memory. The gap is momentum: the distance between knowing Tuesday is a lifting day and actually being under the bar on Tuesday. So when I decided to add a fitness app to my portfolio, I skipped the categories the big players own and built for the one metric my friends and I actually lose sleep over. Showing up. This is the build story, the stack, and the part where I admit the builder broke his own rule.&lt;/p&gt;

&lt;h2&gt;
  
  
  The design decision that shaped everything
&lt;/h2&gt;

&lt;p&gt;MyFitnessPal will count your macros to the gram. Whoop will grade your sleep. Strava will rank you against strangers on a hill. All of that is optimization tooling, and optimization tooling quietly assumes the workout already happened.&lt;/p&gt;

&lt;p&gt;Momentum measures whether the workout happened. Sessions logged, consistency over time, credit for showing up rather than a grade on how optimal the session was. A missed Tuesday should cost you a data point, and in most trackers it costs you the whole perfect chain (you know the uninstall I mean, the one you do a little ashamed at week six). Consistency for people over 40 has to survive real life: travel weeks, a brutal quarter, a knee that says no. So the target is showing up, because for my crowd that was always the real boss fight.&lt;/p&gt;

&lt;h2&gt;
  
  
  The stack, for the curious
&lt;/h2&gt;

&lt;p&gt;The front end is React, generated and iterated through Lovable, which is how I ship UI as a solo builder without losing a month to component libraries. Supabase runs the back end: Postgres, auth, and row-level security doing the actual work. I keep choosing Supabase across the portfolio for a boring reason: the database is the product in an app like this, and getting Postgres, policies, and edge functions in one place means the security review is one review instead of five. Stripe handles billing on the web, with a free tier that covers your first habit and two paid tiers at $3.99 and $7.99 a month. There is a Capacitor shell for the iOS build, which has been its own education in provisioning profiles (a story for a different post, probably a long one).&lt;/p&gt;

&lt;p&gt;The deliberate constraint across all seven apps is that the stack stays ordinary. Lovable or Vite on the front, Supabase behind it, Stripe for money, GitHub Actions for anything scheduled. Durable beats clever when one person is on call for everything, and every exotic dependency is a 2am page waiting for its moment.&lt;/p&gt;

&lt;h2&gt;
  
  
  The honest part
&lt;/h2&gt;

&lt;p&gt;Momentum is the least-promoted thing in my portfolio. Before this post it had been mentioned publicly three times, while the loudest of its sibling apps has collected more than thirty. I built it quietly and then let louder apps cut in line, which is a strange thing to admit about a product whose whole thesis is consistency. The builder failed the app's own test: knowledge was never the gap, showing up was.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd do differently, and what's next
&lt;/h2&gt;

&lt;p&gt;I would promote from day one, in public, before the app felt ready. The apps I talked about early grew faster at the same level of polish, and the compounding never started for the one I kept in a drawer. Next is exactly that correction: Momentum gets a regular slot in the rotation, and I start writing about the retention data once there is enough of it to be worth your time.&lt;/p&gt;

&lt;p&gt;The metric I care about is the one the app preaches: weekly actives who log a session, week after week. Downloads flatter you and screenshots flatter the product, and neither one tells you whether a 52-year-old with a bad knee and a full calendar came back on a rainy Tuesday. When I have three months of honest numbers on that, good or bad, I will publish them here, because a consistency app that hides its own consistency data would be a punchline I'd rather not become.&lt;/p&gt;

&lt;p&gt;If your own gap is showing up rather than knowing what to do, the first habit is free at momentumfit.app. And if you are building something solo: ship the loud version. The quiet one costs more than it feels like it does.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>From PillPal to CareCadence: A Live Rebrand Across 47 Files and 4 Database Tables</title>
      <dc:creator>Chad Dyar</dc:creator>
      <pubDate>Sat, 18 Jul 2026 16:28:11 +0000</pubDate>
      <link>https://dev.to/chadtdyar/from-pillpal-to-carecadence-a-live-rebrand-across-47-files-and-4-database-tables-4gfd</link>
      <guid>https://dev.to/chadtdyar/from-pillpal-to-carecadence-a-live-rebrand-across-47-files-and-4-database-tables-4gfd</guid>
      <description>&lt;p&gt;Technical post-mortem of renaming a production Lovable app. What broke: stale URLs in 47 files, Supabase table references, Stripe product mappings, Cloudflare DNS cutover, Sentry project rename. The grep-across-second-brain pattern that should have run at rename time. Lessons for any indie builder doing a rebrand.&lt;/p&gt;

</description>
      <category>pethealth</category>
      <category>dogowners</category>
      <category>pawformance</category>
      <category>buildinpublic</category>
    </item>
  </channel>
</rss>
