<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Home on Eric Irwin</title><link>http://ericirwin.io/</link><description>Recent content in Home on Eric Irwin</description><generator>Hugo</generator><language>en-us</language><managingEditor>Eric.Irwin@gmail.com (Eric Irwin)</managingEditor><webMaster>Eric.Irwin@gmail.com (Eric Irwin)</webMaster><lastBuildDate>Sat, 07 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://ericirwin.io/index.xml" rel="self" type="application/rss+xml"/><item><title>Borrowing from Team Topologies to Make Sense of Claude Agent Teams</title><link>http://ericirwin.io/posts/borrowing-from-team-topologies-for-claude-agent-teams/</link><pubDate>Sat, 07 Feb 2026 00:00:00 +0000</pubDate><author>Eric.Irwin@gmail.com (Eric Irwin)</author><guid>http://ericirwin.io/posts/borrowing-from-team-topologies-for-claude-agent-teams/</guid><description>&lt;p&gt;There&amp;rsquo;s a habit I can&amp;rsquo;t turn off. Whenever I&amp;rsquo;m working on something — whether it&amp;rsquo;s organizing a project, structuring a team, or just figuring out how to approach a problem — my brain immediately goes to: &lt;em&gt;what&amp;rsquo;s the optimal shape for this?&lt;/em&gt; What information needs to flow, and between whom? Where are the boundaries?&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s the kind of thinking that Matthew Skelton and Manuel Pais gave a name and a framework to with &lt;em&gt;Team Topologies&lt;/em&gt;. If you haven&amp;rsquo;t read it, the short version is that it offers a set of mental models for how engineering teams should be structured — and not around org charts, but around the flow of value. How teams communicate, where cognitive load sits, what interaction modes make sense for a given type of work. It fundamentally changed how I think about engineering organizations, and honestly, it&amp;rsquo;s one of those frameworks that keeps paying dividends years after you first encounter it.&lt;/p&gt;</description></item><item><title>The Case for Making Your AI Tools Argue With Each Other</title><link>http://ericirwin.io/posts/the-case-for-making-your-ai-tools-argue-with-each-other/</link><pubDate>Sat, 24 Jan 2026 00:00:00 +0000</pubDate><author>Eric.Irwin@gmail.com (Eric Irwin)</author><guid>http://ericirwin.io/posts/the-case-for-making-your-ai-tools-argue-with-each-other/</guid><description>&lt;p&gt;We&amp;rsquo;ve gotten pretty comfortable trusting LLM output. The answers sound authoritative. The code compiles. The reasoning feels right. And then we ship it. But the most dangerous thing an AI can do isn&amp;rsquo;t give you a wrong answer. The problem isn&amp;rsquo;t &amp;ldquo;AI is sometimes wrong.&amp;rdquo; It&amp;rsquo;s that we keep asking one model to be the authority.&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s what pushed me into a little experiment: instead of using an LLM like an answer machine, what if I used it like a decision stress test?&lt;/p&gt;</description></item><item><title>The Real Bottleneck in AI Isn't the Model — It's Our Communication</title><link>http://ericirwin.io/posts/the-real-bottleneck-in-ai-isnt-the-model/</link><pubDate>Thu, 27 Nov 2025 00:00:00 +0000</pubDate><author>Eric.Irwin@gmail.com (Eric Irwin)</author><guid>http://ericirwin.io/posts/the-real-bottleneck-in-ai-isnt-the-model/</guid><description>&lt;p&gt;We&amp;rsquo;re living through one of the fastest paradigm shifts in modern computing. Tools are getting better, models are getting smarter, and the ecosystem is moving from prompt engineering toward something far more powerful: context engineering.&lt;/p&gt;
&lt;p&gt;But even as the tooling evolves quickly it is clear that some people get extraordinary results out of AI tools&amp;hellip; and others get diminishing returns.&lt;/p&gt;
&lt;p&gt;And when you peel the layers back, the reason is surprisingly human. It&amp;rsquo;s almost always about how effectively they communicate with the machine and how unnatural that still feels for most of us.&lt;/p&gt;</description></item><item><title>The AI-First Engineering Pattern: How Persistent Context Turns Claude into a True Teammate</title><link>http://ericirwin.io/posts/the-ai-first-engineering-pattern/</link><pubDate>Sat, 25 Oct 2025 00:00:00 +0000</pubDate><author>Eric.Irwin@gmail.com (Eric Irwin)</author><guid>http://ericirwin.io/posts/the-ai-first-engineering-pattern/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Building a platform like Swoop means juggling a mobile app, dashboards, APIs, infrastructure, and — more recently — AI agents. Over time, I built a workflow using Claude Code that treats all of it as one intelligent workspace: a single place where code, data, operations, and testing are deeply connected.&lt;/p&gt;
&lt;p&gt;The key insight: AI becomes genuinely useful when it shares your mental model of the system.&lt;/p&gt;
&lt;p&gt;When architecture, tooling, and context are explicit, Claude stops acting like autocomplete and starts reasoning like a teammate who understands your entire environment. This isn&amp;rsquo;t about clever prompts — it&amp;rsquo;s about teaching your workspace to think in context.&lt;/p&gt;</description></item><item><title>The Quiet Evolution of AI Tools: From Autocomplete to Workflow Bridges</title><link>http://ericirwin.io/posts/the-quiet-evolution-of-ai-tools/</link><pubDate>Thu, 02 Oct 2025 00:00:00 +0000</pubDate><author>Eric.Irwin@gmail.com (Eric Irwin)</author><guid>http://ericirwin.io/posts/the-quiet-evolution-of-ai-tools/</guid><description>&lt;p&gt;AI is one of the most polarizing topics in engineering right now. For some, it represents a threat to jobs or a black box risk; for others, it&amp;rsquo;s the next great productivity revolution. But beneath the noise, there&amp;rsquo;s a more subtle — and in many ways more exciting — shift underway: the evolution of AI tools like Cursor and Claude into customizable workflow partners.&lt;/p&gt;
&lt;p&gt;Instead of being just autocomplete engines, these tools are learning how to meet us exactly where we are. Through hooks, sub-agents, and local context, they&amp;rsquo;re becoming bridges across the many layers and abstractions engineers have to navigate daily.&lt;/p&gt;</description></item><item><title>Generative AI vs. Agents: A Simple Litmus Test</title><link>http://ericirwin.io/posts/generative-ai-vs-agents-a-simple-litmus-test/</link><pubDate>Tue, 09 Sep 2025 00:00:00 +0000</pubDate><author>Eric.Irwin@gmail.com (Eric Irwin)</author><guid>http://ericirwin.io/posts/generative-ai-vs-agents-a-simple-litmus-test/</guid><description>&lt;p&gt;I&amp;rsquo;m writing this because I&amp;rsquo;ve made the mistake myself. I assumed everything should be an agent. If there was a problem to solve, my first instinct was, &lt;em&gt;let&amp;rsquo;s build an agent for that.&lt;/em&gt; It took running headfirst into the tradeoffs — performance, debugging headaches, and unnecessary complexity — for me to realize that not everything benefits from being &lt;em&gt;agentic.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;And honestly, this isn&amp;rsquo;t a new struggle. We&amp;rsquo;ve seen the same pattern with AI more broadly: reaching for it to solve problems that are often handled better with simpler, more traditional approaches. Now, agents and agentic systems are following the same trajectory — being turned to as the &amp;ldquo;solution&amp;rdquo; even when they&amp;rsquo;re not the right fit. Or at least not the immediate.&lt;/p&gt;</description></item><item><title>IDPs For The Rest of Us: Maximizing Impact When You Aren't a Tech Giant</title><link>http://ericirwin.io/posts/idps-for-the-rest-of-us/</link><pubDate>Sun, 17 Nov 2024 00:00:00 +0000</pubDate><author>Eric.Irwin@gmail.com (Eric Irwin)</author><guid>http://ericirwin.io/posts/idps-for-the-rest-of-us/</guid><description>&lt;p&gt;At BackstageCon 2024, I was fortunate to have the opportunity to share how Quantum Metric has maximized the value of its Internal Developer Platform (IDP) by leveraging Backstage. For those who couldn&amp;rsquo;t attend, I&amp;rsquo;ve consolidated the key insights here in written format.&lt;/p&gt;
&lt;p&gt;The presentation can be viewed 
&lt;a href="https://www.youtube.com/results?search_query=backstagecon&amp;#43;2024&amp;#43;quantum&amp;#43;metric&amp;#43;eric&amp;#43;irwin" target="_blank" rel="noopener"&gt;here&lt;/a&gt;
.&lt;/p&gt;
&lt;p&gt;We will cover:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Our journey in rethinking platform strategy and selecting Backstage as our IDP.&lt;/li&gt;
&lt;li&gt;An overview of custom plugins we&amp;rsquo;ve built, highlighting our approach to defining key metrics and validating their impact.&lt;/li&gt;
&lt;li&gt;Key themes and takeaways that have been instrumental for our team and can provide value at any stage of your IDP journey.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="rethinking-our-platform-strategy"&gt;Rethinking our Platform Strategy&lt;/h2&gt;
&lt;p&gt;Quantum Metric enables organizations to understand and prioritize what matters most by capturing real-time customer insights. With a rapidly growing product and customer base, maintaining efficiency and scalability while staying lean has always been a top priority.&lt;/p&gt;</description></item><item><title>Introducing the Quantum Metric Analytics Plugin for Backstage</title><link>http://ericirwin.io/posts/introducing-quantum-metric-analytics-plugin-for-backstage/</link><pubDate>Wed, 20 Mar 2024 00:00:00 +0000</pubDate><author>Eric.Irwin@gmail.com (Eric Irwin)</author><guid>http://ericirwin.io/posts/introducing-quantum-metric-analytics-plugin-for-backstage/</guid><description>&lt;p&gt;At Quantum Metric, the concept of dog fooding, or using our own products to solve our problems, has been a cornerstone of our product development process.&lt;/p&gt;
&lt;p&gt;Since the beginning of our journey with Backstage, our team has always valued a deeper understanding of user engagement and behavior on the platform. This approach has enabled us to leverage the power of our own product from the outset, offering us a window into both the quantitative and qualitative aspects of the platform we are building. As our platform has grown and evolved, so has our commitment to refining the data that we capture.&lt;/p&gt;</description></item><item><title>The Power of a Monthly Newsletter</title><link>http://ericirwin.io/posts/the-power-of-a-monthly-newsletter/</link><pubDate>Sat, 16 Mar 2024 00:00:00 +0000</pubDate><author>Eric.Irwin@gmail.com (Eric Irwin)</author><guid>http://ericirwin.io/posts/the-power-of-a-monthly-newsletter/</guid><description>&lt;p&gt;Inspired by Will Larson&amp;rsquo;s approach to 5&amp;ndash;15s, I set a goal for myself a little over a year ago: to initiate a recurring newsletter aimed at offering a glimpse into the ongoing progress and contributions of my team within our organization.&lt;/p&gt;
&lt;p&gt;As I reflect on the last year, the value of this simple communication tool has extended far beyond my initial expectations. With that said, I wanted to share my experience of the benefits that one might expect from incorporating a monthly newsletter into your leadership strategy.&lt;/p&gt;</description></item><item><title>Simplify your Strategic Leadership Framework With These Four Components</title><link>http://ericirwin.io/posts/simplify-your-strategic-leadership-framework/</link><pubDate>Sat, 01 Jul 2023 00:00:00 +0000</pubDate><author>Eric.Irwin@gmail.com (Eric Irwin)</author><guid>http://ericirwin.io/posts/simplify-your-strategic-leadership-framework/</guid><description>&lt;p&gt;I have been fortunate enough in my leadership roles to hit a point where the way in which I was operating was becoming less effective and I recognized I needed to make adjustments in order to allow my teams to be successful. I subtly noticed I was becoming the bottleneck across my teams and needed to operate on a higher level of abstraction in order to get out of my teams way.&lt;/p&gt;</description></item><item><title>System Models in Backstage</title><link>http://ericirwin.io/posts/system-models-in-backstage/</link><pubDate>Thu, 13 Oct 2022 00:00:00 +0000</pubDate><author>Eric.Irwin@gmail.com (Eric Irwin)</author><guid>http://ericirwin.io/posts/system-models-in-backstage/</guid><description>&lt;p&gt;At Quantum Metric, our teams committed to leveraging Backstage within our Developer Experience Platform (or DXP as we refer to it) following a brief but convincing POC. We felt confident in it becoming a critical component within our Platform moving forward.&lt;/p&gt;
&lt;p&gt;We wanted to share our experiences in the early stages of integrating Backstage as well as give some examples for why we felt that it was important to build a strong foundation to support our System Model.&lt;/p&gt;</description></item><item><title>Custom Autoscaling for GitLab Kubernetes Executors</title><link>http://ericirwin.io/posts/custom-autoscaling-for-gitlab-kubernetes-executors/</link><pubDate>Mon, 10 Jan 2022 00:00:00 +0000</pubDate><author>Eric.Irwin@gmail.com (Eric Irwin)</author><guid>http://ericirwin.io/posts/custom-autoscaling-for-gitlab-kubernetes-executors/</guid><description>&lt;p&gt;I recently had the opportunity to share some really interesting work that our team at Quantum Metric was doing to improve the performance and reliability of our GitLab CI pipelines.&lt;/p&gt;
&lt;p&gt;The intention of this article is to provide an overview of why and how our team decided to implement our own custom autoscaling for our GitLab CI jobs running on Kubernetes.&lt;/p&gt;
&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Our engineering organization has evolved significantly over the past three years. We have experienced rapid growth within our teams as well as our customer base and we continue to improve how we are delivering value quickly and reliably to our customers.&lt;/p&gt;</description></item><item><title>About</title><link>http://ericirwin.io/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>Eric.Irwin@gmail.com (Eric Irwin)</author><guid>http://ericirwin.io/about/</guid><description>&lt;h2 id="background"&gt;Background&lt;/h2&gt;
&lt;p&gt;I was born and raised in Arizona and received my undergraduate degree at 
&lt;a href="https://www.citadel.edu/" target="_blank" rel="noopener"&gt;The Citadel&lt;/a&gt;
, The Military College of South Carolina, where I graduated Cum Laude with a B.S. in Computer Science and a Minor in Management Information Systems in just three years.&lt;/p&gt;
&lt;p&gt;After graduating, I returned to Arizona and earned my Masters of Science in Software Engineering from 
&lt;a href="https://www.asu.edu/" target="_blank" rel="noopener"&gt;Arizona State University&lt;/a&gt;
, with a focus on Distributed Systems.&lt;/p&gt;
&lt;h2 id="career"&gt;Career&lt;/h2&gt;
&lt;p&gt;In March 2019, I began my current role at 
&lt;a href="https://www.quantummetric.com/" target="_blank" rel="noopener"&gt;Quantum Metric&lt;/a&gt;
 in Denver, CO. I&amp;rsquo;ve been fortunate to work with incredibly talented engineers and innovative teams throughout my career, spanning companies like Carvana, CommercialTribe, and others across the Denver and Phoenix tech scenes.&lt;/p&gt;</description></item><item><title>Experience</title><link>http://ericirwin.io/experience/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>Eric.Irwin@gmail.com (Eric Irwin)</author><guid>http://ericirwin.io/experience/</guid><description>&lt;h2 id="quantum-metric"&gt;Quantum Metric&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Senior Director of Engineering&lt;/strong&gt; | Spring 2019 - Present | Denver, CO&lt;/p&gt;
&lt;p&gt;Enthusiastic engineer, leader and learner with a passion for professional and personal development. I believe that highly functioning organizations start at their foundation. Optimizing for transparency ensures teams and individuals possess a deep understanding of larger organizational initiatives. I care deeply about continuous improvement to how teams build, release and iterate on products they own.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="commercialtribe"&gt;CommercialTribe&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Site Reliability Engineer | Sr. Software Engineer&lt;/strong&gt; | Fall 2016 - Spring 2019 | Denver, CO&lt;/p&gt;</description></item><item><title>Featured</title><link>http://ericirwin.io/featured/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>Eric.Irwin@gmail.com (Eric Irwin)</author><guid>http://ericirwin.io/featured/</guid><description>&lt;h2 id="talks"&gt;Talks&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;
&lt;a href="https://www.youtube.com/watch?v=9qPsuMSw_dM" target="_blank" rel="noopener"&gt;IDPs For The Rest of Us: Maximizing Impact When You Aren&amp;rsquo;t a Tech Giant&lt;/a&gt;
&lt;/strong&gt; — My KubeCon talk on building an effective Internal Developer Platform without the resources of a tech giant.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="press"&gt;Press&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;
&lt;a href="https://builtin.com/articles/inside-engineering-teams-leading-next-wave-ai-innovation" target="_blank" rel="noopener"&gt;Inside the Engineering Teams Leading the Next Wave of AI Innovation&lt;/a&gt;
&lt;/strong&gt; — Featured in Built In&amp;rsquo;s look at how engineering teams are leveraging AI to build products more efficiently.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;
&lt;a href="https://www.forrester.com/report/originated-by-spotify-backstage-sparks-a-platform-revolution/RES182394" target="_blank" rel="noopener"&gt;Originated by Spotify, Backstage Sparks a Platform Revolution&lt;/a&gt;
&lt;/strong&gt; — Eric&amp;rsquo;s KubeCon talk on how our engineering teams use QM to validate and measure platform impact.&lt;/p&gt;</description></item></channel></rss>