<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Posts on Clayton Davis Blog</title>
    <link>https://blog.claytondavis.dev/post/</link>
    <description>Recent content in Posts on Clayton Davis Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 16 Nov 2026 08:00:00 -0600</lastBuildDate><atom:link href="https://blog.claytondavis.dev/post/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Anyone Can Build an App. That&#39;s Why Product and Design Matter More Than Ever.</title>
      <link>https://blog.claytondavis.dev/post/012-anyone-can-build-an-app/</link>
      <pubDate>Mon, 16 Nov 2026 08:00:00 -0600</pubDate>
      
      <guid>https://blog.claytondavis.dev/post/012-anyone-can-build-an-app/</guid>
      <description>AI is fundamentally changing the economics of software development. What used to take months can now be prototyped in days. What used to require a team of engineers can sometimes be accomplished by one person with Claude and a good prompt.
That&amp;rsquo;s incredible. But it also creates a problem.
When everyone can build software, simply building software is no longer a competitive advantage.
I believe this is going to fundamentally change how we think about application development.</description>
    </item>
    
    <item>
      <title>Enabling an AI-Powered SDLC by Shifting Left</title>
      <link>https://blog.claytondavis.dev/post/011-ai-sdlc-shift-left/</link>
      <pubDate>Tue, 28 Oct 2025 08:00:00 -0500</pubDate>
      
      <guid>https://blog.claytondavis.dev/post/011-ai-sdlc-shift-left/</guid>
      <description>Enabling an AI-Powered SDLC by Shifting Left Why the bottleneck isn’t your engineers—it’s your requirements.
If your AI-enablement rollout starts and ends with “developer enablement,” you’ll hit a ceiling fast. Sustainable acceleration happens when product and engineering co-author richer requirements and context—up front—so AI can one-shot features instead of thrashing on code iterations. The Core Idea: Spend Cycles Where They Compound In a traditional flow, we rush scope, write a thin ticket, and toss it over the wall to get it done fast.</description>
    </item>
    
    <item>
      <title>Beyond Story Points: How to Prove Productivity Gains in an AI-Enabled SDLC</title>
      <link>https://blog.claytondavis.dev/post/010-ai-sdlc-measuring-productivity/</link>
      <pubDate>Mon, 11 Aug 2025 08:00:00 -0500</pubDate>
      
      <guid>https://blog.claytondavis.dev/post/010-ai-sdlc-measuring-productivity/</guid>
      <description>Third instalment in the “AI-Powered Engineering” series
You can see part 1 here and part 2 here
TL;DR
 Traditional agile metrics are fallible under AI acceleration and need to be reworked. Swap opinion-based inputs (story points) for data you can’t game: flow, quality, complexity, and experience. Instrument before your first AI pilot or you’ll be chasing a moving baseline forever.  Why “Show Me the Numbers” Suddenly Matters Gen AI promises 2-10x output per engineer, but finance, security, and HR still ask the same question: “How do we know?</description>
    </item>
    
    <item>
      <title>Part 2 — Quality in the Age of LLMs</title>
      <link>https://blog.claytondavis.dev/post/009-ai-sdlc-quality/</link>
      <pubDate>Mon, 04 Aug 2025 08:00:00 -0500</pubDate>
      
      <guid>https://blog.claytondavis.dev/post/009-ai-sdlc-quality/</guid>
      <description>You can see part 1 here
“Ship faster, break… nothing.”
In Part 1 we argued that AI collapses the gap between strategy and execution. The obvious next question: How do we keep quality high when code ships every hour? This post unpacks why classical Test-Driven Development (TDD) isn’t dead—but it is mutating—and how richer, AI-refined requirements become the new guardrail against hallucinations and regressions.
Why Speed Amplifies Quality Risk GenAI reduces the marginal cost of an iteration.</description>
    </item>
    
    <item>
      <title>From Strategy-Led to Hybrid: How AI Is Re-Wiring the First Mile of Software Delivery</title>
      <link>https://blog.claytondavis.dev/post/008-ai-sdlc-hybrid-approach/</link>
      <pubDate>Mon, 28 Jul 2025 08:00:00 -0500</pubDate>
      
      <guid>https://blog.claytondavis.dev/post/008-ai-sdlc-hybrid-approach/</guid>
      <description>Introduction: Planning vs. Building, Redux For the past few decades, enterprise software teams followed a familiar rhythm:
 Product strategy first. Nail the market, persona, features, roadmap. Ensure the thing you are building has a place. Design strategy next. Map user journeys, retention loops, and KPIs. Building out screens as a first pass to solicit feedback as a way to “dip your toe in” Engineering last. Kick-off happens months—sometimes a full year—after the first discovery workshop.</description>
    </item>
    
    <item>
      <title>Mobile App - Building a mobile app</title>
      <link>https://blog.claytondavis.dev/post/007-mobile-apps/</link>
      <pubDate>Tue, 29 Nov 2022 08:00:00 -0500</pubDate>
      
      <guid>https://blog.claytondavis.dev/post/007-mobile-apps/</guid>
      <description>In 2022 over half of the traffic on the internet is generated by mobile devices. And behind a majority of those devices are users who prefer mobile-friendly/mobile-first development, and if they don&amp;rsquo;t get it they are likely to take their business elsewhere. This is not a new trend, but a trend that continues to become more and more prominent. Now we could talk about why this is or how it affects the industry, but I really just wanted to use it as a segway into this blog.</description>
    </item>
    
    <item>
      <title>Infrastructure As Code</title>
      <link>https://blog.claytondavis.dev/post/006-infrastructure-as-code/</link>
      <pubDate>Sun, 16 Oct 2022 08:00:00 -0500</pubDate>
      
      <guid>https://blog.claytondavis.dev/post/006-infrastructure-as-code/</guid>
      <description>Can also see this blog post on the Caylent blog
Part of my day-to-day job is reviewing proposals for our sales team prior to them presenting them to our clients. One of the things I see in 99.9% of proposals is Infrastructure as Code (IaC). Even if a customer can&amp;rsquo;t spell IaC, at some point during the sales cycle, we convince them that it is critical to their success in the cloud.</description>
    </item>
    
    <item>
      <title>One year at Caylent</title>
      <link>https://blog.claytondavis.dev/post/005-one-year-at-caylent/</link>
      <pubDate>Tue, 10 May 2022 08:00:00 -0500</pubDate>
      
      <guid>https://blog.claytondavis.dev/post/005-one-year-at-caylent/</guid>
      <description>Today marks my one year at Caylent. Milestones often call for reflections, so let&amp;rsquo;s reflect.
While the company was new to me one year ago, the job was one I very familiar with. Cloud consulting, and more specifically AWS consulting, has been my life for the last almost 2100 days. I worked my way through all of the IC roles you could and delivered on dozens of projects across dozen of clients.</description>
    </item>
    
    <item>
      <title>Monoliths. What are they good for?</title>
      <link>https://blog.claytondavis.dev/post/004-monoliths-what-are-they-good-for/</link>
      <pubDate>Mon, 02 May 2022 08:00:00 -0500</pubDate>
      
      <guid>https://blog.claytondavis.dev/post/004-monoliths-what-are-they-good-for/</guid>
      <description>I recently took a new role as the director of the Cloud-Native Applications team at Caylent. This team is in charge of not only helping our clients build new applications but also modernizing their existing applications to better leverage the cloud. This DOES NOT mean we help our client pick up a monolithic application and all of its coupled dependencies and migrate it to an EC2 instance (we have another team for that).</description>
    </item>
    
    <item>
      <title>Custom Built Email Subscription</title>
      <link>https://blog.claytondavis.dev/post/003-custom-built-email-subscription/</link>
      <pubDate>Fri, 25 Mar 2022 08:00:00 -0500</pubDate>
      
      <guid>https://blog.claytondavis.dev/post/003-custom-built-email-subscription/</guid>
      <description>Everyone can calm down now, email notifications are here. So many of you (it was one person) have been asking for it. And if I am being honest, what blog doesn&amp;rsquo;t have a subscribe feature. Silly, super easy to use and deploy framework that doesn&amp;rsquo;t have a built-in subscribe feature (because it requires no infrastructure). Anyway - this post will walk you through how I built this custom, cloud-native, serverless, buzzword buzzword, subscribe feature.</description>
    </item>
    
    <item>
      <title>Why Everyone Should Use AWS Control Tower</title>
      <link>https://blog.claytondavis.dev/post/002-why-everyone-should-use-ct/</link>
      <pubDate>Mon, 21 Mar 2022 09:00:00 -0600</pubDate>
      
      <guid>https://blog.claytondavis.dev/post/002-why-everyone-should-use-ct/</guid>
      <description>My life for the past 10 months has involved a lot of AWS Control Tower. I helped build the Control Tower Catalyst at Caylent and have been involved in delivering, selling, or troubleshooting it well over two dozen times at this point. Prior to joining Caylent, I knew at a high level what Control Tower was and why enterprises might use it, but I had very little hands on with it and didn&amp;rsquo;t care for much.</description>
    </item>
    
    <item>
      <title>How did I build this blog?</title>
      <link>https://blog.claytondavis.dev/post/001-how-did-i-build-this-blog/</link>
      <pubDate>Wed, 09 Mar 2022 12:00:00 -0600</pubDate>
      
      <guid>https://blog.claytondavis.dev/post/001-how-did-i-build-this-blog/</guid>
      <description>For the first blog, less of an opinion piece and more of a “how does this work” piece. I will run through how I set up this blog.
Requirements As with any good project, I started off with a few requirements for this blog.
The first was the ability to host this in a serverless environment (S3, Cloudfront, Lambda, etc). I don&amp;rsquo;t expect much traffic to this blog and I wanted to keep my cost down.</description>
    </item>
    
  </channel>
</rss>
