<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Rick Fast on Medium]]></title>
        <description><![CDATA[Stories by Rick Fast on Medium]]></description>
        <link>https://medium.com/@rickfast?source=rss-692f5e1aa63f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*xhe3Hoe0Z4_hSnsh.</url>
            <title>Stories by Rick Fast on Medium</title>
            <link>https://medium.com/@rickfast?source=rss-692f5e1aa63f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 18:27:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rickfast/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Just Because We Can Build It, Should We?]]></title>
            <link>https://medium.com/expedia-group-tech/just-because-we-can-build-it-should-we-a292fbdd22ce?source=rss-692f5e1aa63f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a292fbdd22ce</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[platform]]></category>
            <category><![CDATA[engineering-leadership]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Rick Fast]]></dc:creator>
            <pubDate>Tue, 05 May 2026 11:01:01 GMT</pubDate>
            <atom:updated>2026-05-05T11:01:01.694Z</atom:updated>
            <content:encoded><![CDATA[<h4><a href="https://medium.com/expedia-group-tech/subpage/platform">Expedia Group Technology — Platform</a></h4><h4><strong>How AI changed the build vs. buy equation, and why discipline matters more than ever</strong></h4><figure><img alt="A hiker viewed from behind holding a compass, standing in an open landscape" src="https://cdn-images-1.medium.com/max/1024/0*H8MhgBKBcrZGZZEc" /><figcaption>Photo by Ali Kazal on Unsplash</figcaption></figure><p>Agentic coding tools and AI-native workflows have changed what’s possible for platform engineering teams. I lead Platform Engineering at <a href="https://www.expediagroup.com/">Expedia Group</a>™, one of the world’s largest travel technology companies. We power brands like Expedia®, Hotels.com®, Vrbo®, Orbitz®, and Travelocity®. My organization builds the technology that all of these brands and their partners run on: APIs, data and AI services, developer tools, CI/CD infrastructure, and the shared capabilities that let thousands of engineers ship reliably at scale.</p><p>For many greenfield problems, it now feels like we can build almost anything from scratch with a fraction of the effort it used to take. But that creates a harder question: <strong>just because we can build it, should we?</strong></p><h4><strong>The temptation is real</strong></h4><p>When you lead a platform organization and your engineers suddenly have access to powerful agentic coding assistants, the possibilities open up fast. It’s tempting to look at SaaS products your company is paying for and think, “We could build that in a weekend.”</p><p>And honestly? In many cases, you probably could stand something up quickly. The initial build cost has dropped through the floor.</p><p>But building something and <em>owning</em> something are very different decisions. That’s where the new calculus gets interesting.</p><h4><strong>The hidden cost of owning software</strong></h4><p>Vendors aren’t just shipping features. They’re maintaining the software, fixing bugs and edge cases you haven’t thought about yet, and improving the UX across thousands of customers with different requirements. Mature platforms have decades of accumulated work behind them: production hardening, compliance, operational tooling, and long-tail requirements you’d only discover slowly through real-world use.</p><p>You can’t clone that maturity quickly, even if the initial build feels cheap thanks to AI. <strong>The build side of the equation has changed dramatically, but the own-and-operate side has not changed nearly as much.</strong></p><p>There are cases where the calculus does shift. Some products are undifferentiated and low value; they don’t justify ongoing spend when simpler alternatives exist. For those, it may make sense to stop paying and either build a lightweight replacement or simplify. But that’s a very different posture than “we can build everything now, so we should.”</p><h4><strong>Our AI platform strategy: what we actually did</strong></h4><p>Last year, we made an explicit strategic decision in our AI platform work: stop implementing everything from the ground up internally, and instead lean into composable, external building blocks.</p><p>We had previously built bespoke AI platforms in-house. Custom orchestration layers and gateways, proprietary memory systems, internal agent frameworks. They worked, but they came with heavy maintenance costs and, more importantly, they fell behind the pace of the broader AI ecosystem.</p><p>So we changed direction:</p><ul><li><strong>We adopted an AI platform architecture</strong> that uses open standards and vendor ecosystems, such as n8n and LangSmith, rather than proprietary abstractions.</li><li><strong>We simplified our LLM proxy layer</strong> by swapping in an off-the-shelf routing product (LiteLLM) instead of maintaining a fully custom implementation.</li><li><strong>We replaced our in-house agent memory system</strong> with a cloud-native composable alternative (such as AWS’s Agent Core memory), treating it as a pluggable component rather than another platform we’d have to run forever.</li></ul><p>The principles behind these moves:</p><ol><li><strong>Composability matters most.</strong> Our ecosystem is complex. We need building blocks that fit together cleanly across dozens of teams and product lines.</li><li><strong>Don’t abstract away vendor progress.</strong> The AI space moves extremely fast. If you build thick proprietary abstractions on top of vendor frameworks, you’ll always be behind their latest capabilities. You end up maintaining a translation layer instead of shipping value.</li><li><strong>Turnkey integrations, thin layers.</strong> Make integration easy and batteries-included, but don’t build heavy opinionated layers that freeze you in place.</li></ol><p>Since the pivot, teams have picked up new AI capabilities faster, we spend less time rebuilding what others already provide, and we can actually keep up with improvements from frameworks and vendors as they ship.</p><h4><strong>The broader lesson: what this means for platform teams</strong></h4><p>This applies well beyond AI platforms. As a platform engineering organization, building platform technology is our core job, and agentic tooling has made that a lot easier. But that doesn’t mean everything we <em>could</em> turn into a platform <em>should</em> become one.</p><p>If you over-platformize, you risk creating an internal marketplace of cool tech that isn’t aligned with near-term business goals and doesn’t have clear owners or long-term roadmaps. You anchor to local inventions that the broader industry doesn’t converge on, so you’re maintaining something proprietary while everyone else moves in a different direction. You raise the abstraction bar so high that teams can’t adopt new external capabilities when they emerge. In short: you can end up slowing your company down in the name of moving fast.</p><h4><strong>How we decide what to build</strong></h4><p>Here’s the framework we’re applying across Platform Engineering at Expedia Group.</p><h4><strong>Start from team priorities, not technical possibilities</strong></h4><p>Before building a new platform capability, ask: <em>What specific team priority does this support? What goals are we trying to achieve in the next 12–18 months? Is this the best use of time for those goals, or just an interesting technical opportunity?</em></p><h4><strong>Build for your own domain first</strong></h4><p>When you build, optimize for your domain problem: your runbooks, your incident patterns, your critical flows. Don’t pre-optimize for everyone else’s domains. Other teams now have access to the same AI building blocks and can solve their own problems. If your solution becomes obviously valuable and reusable, you can look at platformizing it later, deliberately.</p><p>A good mental check: <em>if this didn’t exist, would my team still have a hard, recurring problem next quarter?</em> If the answer is “not really,” it’s probably not where you should invest platform cycles.</p><h4><strong>Favor composable primitives over monolithic platforms</strong></h4><p>Across our AI and platform work, the primitives that are working best:</p><ul><li><strong>Skills</strong>: Small, composable chunks of procedural and domain knowledge. Easy to share across repos, tools, and teams without creating hard dependencies.</li><li><strong>API servers with standard protocols + CLI’s</strong>: Standardized ways to expose domain capabilities into agentic workflows. Model Context Protocol (MCP) is an open standard for connecting AI assistants to external tools and data, and it’s gaining real traction here. It works naturally for both coding and non-coding use cases.</li><li><strong>Agents designed for compatibility</strong>: Scoped to specific problem domains or workflows (CI/CD, incident response, deployment orchestration) and built to load the right skills and connect to the right services automatically.</li></ul><p>These are low-regret bets. They compose well with multiple tools and coding agents, stay close to open standards, and are easier to replace or upgrade than monolithic platforms.</p><p><strong>A concrete example</strong>: Picture a CI/CD agent that picks up work after a pull request is merged and handles higher-level deployment workflows: interpreting pipeline configurations, managing rollbacks, handling approvals, calling standardized deployment APIs. Back it with composable skills and protocol-compliant service integrations, and you get something that stays close to existing platform primitives, evolves as your deployment stack evolves, and can be adapted by other teams without hard-coding all logic into a single bespoke system.</p><h4><strong>The buy side: same discipline, different direction</strong></h4><p>This same calculus applies to vendor and purchasing decisions. In today’s AI market, lots of vendors want you to centralize all your data in their ecosystem and use their proprietary dashboards, agents, and knowledge graphs.</p><p>In a space moving this fast, that creates a different kind of lock-in. Not just with a product, but with your data, workflows, and mental model of how you operate. We’re cautious about all-or-nothing stacks that try to own the entire vertical and platforms that don’t let you swap components in and out.</p><p>Our preferred vendor pattern: <strong>composable offerings</strong> where we can plug a component into our stack, swap it out later if needed, and we’re not forced to centralize everything into a single closed ecosystem. We want the flexibility to adapt as the AI space shifts, because it will shift, repeatedly, and probably faster than any of us expect.</p><h4><strong>The bottom line</strong></h4><p>The calculus of build vs. buy is changing. AI and agentic tools have altered what’s possible and how quickly platform teams can move. But discipline matters more than ever.</p><p>Here’s what we’re telling our teams:</p><ol><li><strong>Keep innovating</strong>, especially on your own workflows. Anything that improves your team’s productivity or simplifies your day-to-day is worth doing, even if it never becomes a broad platform product.</li><li><strong>Be intentional about what you turn into shared platform tech.</strong> Ask what domain problem it solves repeatedly, whether it’s best expressed as a composable primitive, and whether it aligns with the goals you’ve already committed to.</li><li><strong>Stay close to open standards and vendor primitives.</strong> This keeps you compatible with the tools your engineers already gravitate toward and lets you pick up new capabilities as they ship.</li><li><strong>Don’t make yourself the bottleneck.</strong> Your job as a platform team is to amplify industry progress for your company, not get in the way with heavy bespoke platforms that age badly.</li></ol><p>Our competitors have these same capabilities now. The difference won’t be who can build the most. It’ll be who applies that ability most deliberately to the software that actually helps them win.</p><p><em>The author leads Platform Engineering at Expedia Group, where the team builds the technology platform powering travel for millions of people across Expedia, Hotels.com, Vrbo, and other brands worldwide.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a292fbdd22ce" width="1" height="1" alt=""><hr><p><a href="https://medium.com/expedia-group-tech/just-because-we-can-build-it-should-we-a292fbdd22ce">Just Because We Can Build It, Should We?</a> was originally published in <a href="https://medium.com/expedia-group-tech">Expedia Group Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reimagining Platform Engineering for an Agentic Future]]></title>
            <link>https://medium.com/expedia-group-tech/reimagining-platform-engineering-for-an-agentic-future-03e3f378a190?source=rss-692f5e1aa63f------2</link>
            <guid isPermaLink="false">https://medium.com/p/03e3f378a190</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[platform-engineering]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[expedia-group-tech]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Rick Fast]]></dc:creator>
            <pubDate>Tue, 07 Apr 2026 12:50:29 GMT</pubDate>
            <atom:updated>2026-04-07T12:50:29.705Z</atom:updated>
            <content:encoded><![CDATA[<h4><a href="https://medium.com/expedia-group-tech/subpage/engineering">Expedia Group Technology — Engineering</a></h4><h4>When your platform’s next user isn’t human</h4><figure><img alt="Houses along the water" src="https://cdn-images-1.medium.com/max/1024/0*l3aHcuQMPu6Pc8W3" /><figcaption>Photo by Alex Vasey on Unsplash</figcaption></figure><p>Earlier this month I hosted a town hall for <a href="https://www.expediagroup.com/">Expedia Group</a>™ Platform Engineering organization, focused on the rapid progress happening in the agentic coding space, and what it means for us as engineers and as a platform team.</p><p>Our teams are responsible for the horizontal foundations that power Expedia Group: AI and analytics, data, user experience platforms, edge and API platforms, cloud and infrastructure, as well as EG’s developer experience.</p><p>In other words, we own the “platform of platforms” that thousands of engineers build on every day.</p><p>Since late last year, with the arrival of models like Opus and modern deep agent harnesses, we’ve been riding a pretty intense wave of change. Larger context windows and more capable agents have made several things clear. A huge amount of what we call “engineering work” can now be done by agents. The real leverage for humans is shifting toward product thinking, architecture, system design, and context. Our platforms, which were designed for humans, are not yet ready to support agents as a distinct user group.</p><p>This post is about what it means to run a large‑scale platform organization in that world, and how we’re retooling our stack, our interfaces, and even our mental models to support both humans and agents at the same time.</p><h4>The change curve for senior engineers</h4><p>For many engineers, especially those who’ve been in the industry for decades, this isn’t just a new toolchain; it’s a <strong>new inner loop</strong>. We’re asking people to delegate more of the “typing” to agents, spend more time on <em>what</em> we’re building and <em>how it fits</em> into the larger system, and learn how to collaborate with agents as teammates, not just as autocomplete.</p><p>That would be hard enough in a greenfield startup. In a company that runs a large chunk of the online travel ecosystem, it’s even harder. We still must keep the planes in the air: keep sites up, pipelines flowing, and revenue‑critical systems healthy.</p><p>Finding the time and headspace to <strong>change how you work</strong> while you’re doing all of that is non‑trivial.</p><p>One experiment we ran to break through that inertia was something we called <strong>Ralphathon,</strong> a “no‑coding‑allowed” hackathon designed to encourage people to explore what these tools could do <em>without</em> falling back to old patterns. The goal wasn’t to build production‑ready projects; it was to spark curiosity, lower the barrier to experimentation, and give people a safe space to rethink their workflows.</p><p>It worked well enough to confirm a hypothesis: you can’t just <em>tell</em> people to change their inner loop. You have to create the right environment and incentives so they can <em>feel</em> the new way of working.</p><h4>Double duty: Transforming ourselves and the platform</h4><p>Platform engineering is on <strong>double duty</strong>.</p><p>On the one hand, we’re going through the same personal and professional shift as every other engineer: How do these tools change our careers? How do we work more efficiently, productively, and creatively? What does “senior engineer” mean in a world where agents can write most of the code?</p><p>On the other hand, we’re responsible for a platform that was originally built for humans. Expedia Group has been around for decades. Our architectural decisions were optimized around <strong>human constraints</strong>.</p><p>Take microservices. We didn’t split everything into tiny services because it was faster or cheaper. We did it so:</p><ul><li>Teams could deploy independently,</li><li>Work could be done autonomously, and</li><li>We didn’t have thousands of people all crowding into a single repo and stepping on each other’s toes.</li></ul><p>That all made sense in a human‑only world. But in an <strong>agentic</strong> world, some of those same decisions become friction: CI/CD flows that assume a human is in the loop, SDKs and libraries optimized for human ergonomics rather than agent ergonomics, and UIs that are the <em>only</em> way to perform certain critical operations. Our job now is to <strong>fast‑forward the platform</strong> beyond “SDKs + UIs + some APIs for humans” into something that works just as well, if not better, for agents.</p><p>And we must do that while supporting thousands of engineers who are also trying to navigate the same transition.</p><h4>How to Expedia, for agents</h4><p>A concrete example: our <strong>design system</strong>.</p><p>We’ve invested heavily in component libraries across iOS, Android, and web. They allow teams to build reusable modules without worrying about which consumer or B2B brands they’re targeting. The theming, styling, and look‑and‑feel are all handled by the platform. That’s a core capability for a multi‑brand travel platform, and it’s not going away.</p><p>But over time, we layered <strong>proprietary abstractions</strong> on top of standard tech: custom rendering frameworks on top of React, patterns and helpers that are unique to us, and other undifferentiated technology that only exists inside our walls.</p><p>Humans can learn those abstractions. Agents, on the other hand, were trained on the open ecosystem. They “just know” things like Vite, Tailwind CSS, and popular off‑the‑shelf UI libraries and patterns. When we ask an agent to work inside our design system, it can do it, but it doesn’t feel natural. The path of least resistance is to reach for the tools it understands best, which might be <strong>outside</strong> the guardrails we want it to stay within.</p><p>That’s the first kind of problem we must solve: not “How do we add more abstractions?” but “<strong>How do we remove unnecessary ones</strong> so both humans and agents can work with the same primitives more easily?”</p><h4>The hard part isn’t just writing code</h4><p>The second category of friction shows up <strong>after</strong> the code is written.</p><p>Even with current tools, we’re seeing clear gains in how much software can be produced in a given amount of time. Agents are extremely good at generating boilerplate and glue code, translating patterns across services and stacks, and filling in implementation details once the architecture is clear.</p><p>But there’s a lot that happens <strong>between</strong> “code compiles” and “value in production”, including deploying services, running CI/CD pipelines, monitoring workloads, and debugging integration issues across a highly distributed ecosystem.</p><p>Agents are ready and willing to help here, but we haven’t always given them a clean way in.</p><h4>AI finds a way (whether we like it or not)</h4><p>One of the more interesting (and slightly unsettling) things we’ve seen is how <strong>creative</strong> agents can be when you don’t give them proper interfaces. People have asked agents like Claude or others to “watch my pipeline” even when there is no standardized API or integration to do that. The only official way is through a web UI.</p><p>What happens?</p><p>The agent figures out how to log in through the browser, inspects cookies and session state, then navigates the UI as a human would, just faster and more persistently.</p><p>If there’s <em>any</em> way to accomplish the task, the agent will try to find it. From a platform perspective, that’s a signal: if you don’t give agents ergonomic, well‑defined interfaces, they’ll route around you.</p><p>We don’t want to block agents from doing useful work. But we also don’t want our critical operations mediated through brittle browser automation held together by HTML and guesswork.</p><p>So we’ve started to optimize for <strong>agent guardrails</strong>, not <strong>agent roadblocks</strong>.</p><h4>Designing for agent ergonomics</h4><p>This is where <strong>agent ergonomics</strong> becomes a core design principle. Instead of assuming a human is clicking around in a UI, we’re investing in <strong>channels and surfaces that are built for agents</strong> from day one. That includes:</p><p><strong>CLIs designed for agents, not humans<br></strong>We’re building command‑line tools whose primary consumers are agents. They are:</p><ul><li>Easy to introspect.</li><li>Consistent in their inputs and outputs.</li><li>Wired into the systems agents need to operate, including CI/CD, repo management, Kubernetes workloads, logs, and more.</li><li>If there’s a simple, well‑documented way to perform an action via a CLI, an agent will generally prefer that over trying to reverse‑engineer a browser UI.</li></ul><p>One of our first big steps here is a new CLI we call <strong>Tarmac</strong>. It’s an agent‑centric interface that exposes CI/CD operations, repository management, workload monitoring in our Kubernetes clusters, and log exploration and related workflows. Tarmac is built around a simple premise: if an agent can <strong>see</strong> a clean, structured way to operate the platform, it won’t need to invent its own.</p><p><strong>MCP servers and agent‑native protocols <br></strong>We’ve been aggressively rolling out Model Context Protocol (MCP) servers and a registry for our core platform capabilities so agents can:</p><ul><li>Discover what’s possible.</li><li>Call well‑defined operations.</li><li>Get structured responses instead of scraping pages.</li></ul><h4>Reducing agent friction (because it also costs money)</h4><p>Even when agents can figure things out, there’s still <strong>friction</strong>: it takes more steps, burns more tokens, increases latency, and adds complexity to prompts and orchestration. Agent friction is just another form of <strong>platform friction</strong>. We’ve always cared about human ergonomics, i.e. reducing the number of manual steps it takes to ship something. Now we’re doing the same thing for agents.</p><p>One of the most effective tools we’ve found here is <strong>markdown‑based skills and agent definitions. </strong>We encode <em>how</em> to use platform capabilities in a format agents naturally understand by pre‑packaging the “tribal knowledge” that used to live in docs, chats, or individual brains. That lets agents discover and reuse these skills instead of rediscovering how to talk to each service from scratch.</p><p>The net result: agents spend less time fumbling around and more time doing useful work. And the cost profile of that work improves.</p><h4>Internal apps as a safe testbed</h4><p>Some surfaces are too critical or too complex to hand over to agents today. A full consumer‑grade Expedia or Hotels.com experience involves hard production constraints that go far beyond what a Tailwind‑powered prototype can handle.</p><p>But <strong>internal apps</strong> are a very different story. Today, we have Backstage instances running for certain developer experiences, a variety of bespoke UIs built by different platform teams, and a lot of “pretty good” tools that, collectively, still add up to “too many interfaces.” From a builder’s perspective, this means context‑switching between a <strong>lot</strong> of different places to get anything done.</p><p>This is where agents like Claude shine. They’re very good at stitching together internal APIs, they can generate credible UIs quickly when the risk profile is lower, and ignoring which team owns which service. They only care about the underlying concepts.</p><p>We’ve started to lean into that by building a new internal experience we call <strong>Koda. Koda </strong>lives in a <strong>monorepo</strong> dedicated to agent‑built internal apps and focuses on <strong>context engineering</strong>, not on building yet another monolithic platform. It lets agents discover existing APIs, simplify authentication flows on behalf of users, and assemble a <strong>developer console organized around what developers care about</strong>, rather than around our org chart.</p><p>Our role, as humans, shifts from “build the whole thing by hand” to “define the principles and guardrails that agents use to construct and reconstruct these UIs from the ground up.”</p><h4>Where we’re heading, quickly</h4><p>Put all of this together and you get a picture of where we’re aiming over the next year.</p><p><strong>1. Keep the core capabilities battle‑tested</strong></p><p>We’re not trying to rebuild our foundations from scratch. Our core capabilities are differentiators: Deploying and running large‑scale applications, performing analytics over massive datasets, running both streaming and batch data workloads at scale, and powering high‑quality user experiences across hundreds of tenants and brands. Those components need to remain <strong>robust, reliable, and boring</strong> in the best possible way.</p><p><strong>2. Radically change the surface</strong></p><p>Where we <em>do</em> want radical change is at the <strong>surface area. We want to make</strong> <strong>APIs and auth consistent</strong> across the platform, ensure we have <strong>agent‑native channels </strong>such as CLIs like Tarmac, MCP servers, and other structured interfaces designed for automation, and package <strong>skills and agent markdown</strong> in a holistic way so builders, human or agent, can easily discover and use the platform’s capabilities. If you squint, the goal is simple: <strong>make it just as natural for an agent to operate our platform as it is for a human today</strong>.</p><p><strong>3. Embrace new failure modes</strong></p><p>As more agents interact with our systems, we’re going to discover new failure modes, edge cases, and new ways systems can be misused or overused. Instead of fearing that, we’re treating it as <strong>training data for the platform</strong>: When we see agents hacking around UIs, we respond by adding better agent interfaces. When we see complex, brittle flows, we respond by simplifying contracts and tightening guarantees. When we see friction, we respond by improving ergonomics, for both humans and agents. Over time, that feedback loop should give us <strong>more consistent interactions</strong> and <strong>more resilient infrastructure</strong>.</p><h4>Closing thoughts</h4><p>If you run or work in a platform organization today, you’re probably feeling some version of this same tension: You have a ton of battle‑tested capabilities that already work at scale and a new generation of agents that are eager to help but constrained by surfaces that weren’t built for them. You also have humans who need to reinvent their inner loop while keeping the lights on. The temptation is to treat agents as a thin layer on top of your existing tools, a smarter autocomplete or a chat window bolted onto a legacy UI.</p><p>My view is that <strong>agents are a new class of user</strong>, and we need to treat them that way with dedicated interfaces, real ergonomics, and the same care we would give a human user operating at scale.</p><p>At Expedia Group, we’re trying to meet that moment by doing double duty: reshaping how we as engineers work and reshaping the platform that our humans and our agents will share.</p><p>We’re early in that journey, but one thing is already clear: if you don’t design for agents explicitly, they’ll find their own way in anyway. Better to invite them in through the front door.</p><p><a href="https://careers.expediagroup.com/life/">Learn about life at Expedia Group</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=03e3f378a190" width="1" height="1" alt=""><hr><p><a href="https://medium.com/expedia-group-tech/reimagining-platform-engineering-for-an-agentic-future-03e3f378a190">Reimagining Platform Engineering for an Agentic Future</a> was originally published in <a href="https://medium.com/expedia-group-tech">Expedia Group Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>