<?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>AddyOsmani.com</title>
    <description>Addy Osmani is an engineering and evangelism leader who spent over 14 years at Google leading developer experience across Chrome and, in recent years, AI (Gemini, coding agents, and agentic engineering), most recently as a Director at Google Cloud AI.</description>
    <link>https://addyosmani.com</link>
    <atom:link href="https://addyosmani.com/feed.xml" rel="self" type="application/rss+xml" />
    
      <item>
        <title>The Agent-Era Career</title>
        
        
          <description>AI gets good at anything with an answer key. Your career is everything that doesn&apos;t have one.</description>
        
        <pubDate>Mon, 06 Jul 2026 00:00:00 +0000</pubDate>
        <link>https://addyosmani.com/blog/career-advice-age-of-agents/</link>
        <guid isPermaLink="true">https://addyosmani.com/blog/career-advice-age-of-agents/</guid>
      </item>
    
      <item>
        <title>Agentic Autonomy Levels</title>
        
        
          <description>The action in agentic engineering has moved from prompting to operating. Autonomy isn&apos;t one ladder, it&apos;s two axes (agency and orchestration) and six levels you move between per task. The real question is what level a task deserves, and what verification makes that level defensible.</description>
        
        <pubDate>Thu, 02 Jul 2026 00:00:00 +0000</pubDate>
        <link>https://addyosmani.com/blog/agentic-autonomy-levels/</link>
        <guid isPermaLink="true">https://addyosmani.com/blog/agentic-autonomy-levels/</guid>
      </item>
    
      <item>
        <title>The New Software Lifecycle</title>
        
        
          <description>I co-wrote a Google whitepaper about how AI is changing the software lifecycle. I&apos;m not going to summarize the whole thing. Instead, here are the handful of ideas in it I think actually matter, plus six figures you&apos;re welcome to reuse.</description>
        
        <pubDate>Tue, 16 Jun 2026 00:00:00 +0000</pubDate>
        <link>https://addyosmani.com/blog/new-sdlc-vibe-coding/</link>
        <guid isPermaLink="true">https://addyosmani.com/blog/new-sdlc-vibe-coding/</guid>
      </item>
    
      <item>
        <title>Agentic Code Review</title>
        
        
          <description>Coding agents are extraordinarily good now, and getting better fast. The interesting consequence is that the hard part of engineering moved from writing code to deciding whether to trust it, which makes review the most leveraged skill in software right now. How you approach it depends enormously on who you are: a solo developer with no users and a team maintaining a ten-year-old application are not solving the same problem.</description>
        
        <pubDate>Mon, 15 Jun 2026 00:00:00 +0000</pubDate>
        <link>https://addyosmani.com/blog/agentic-code-review/</link>
        <guid isPermaLink="true">https://addyosmani.com/blog/agentic-code-review/</guid>
      </item>
    
      <item>
        <title>Loop Engineering</title>
        
        
          <description>You don&apos;t really need to be good at prompting anymore. The thing to get good at is the loop that does the prompting for you. It&apos;s five building blocks plus somewhere to keep notes, and Codex and Claude Code both have all five now.</description>
        
        <pubDate>Sun, 07 Jun 2026 00:00:00 +0000</pubDate>
        <link>https://addyosmani.com/blog/loop-engineering/</link>
        <guid isPermaLink="true">https://addyosmani.com/blog/loop-engineering/</guid>
      </item>
    
      <item>
        <title>The Intent Debt</title>
        
        
          <description>Technical debt lives in your code. Cognitive debt lives in your head. Intent debt lives in the artifacts you may have never wrote: the goals, constraints, and rationale for why the system is the way it is. If you&apos;re lucky, some of this exists scattered in team documents or discussions, but it&apos;s likely incomplete. It&apos;s the one kind of debt your agents can&apos;t pay down for you, and agentic engineering makes it the most expensive.</description>
        
        <pubDate>Fri, 05 Jun 2026 00:00:00 +0000</pubDate>
        <link>https://addyosmani.com/blog/intent-debt/</link>
        <guid isPermaLink="true">https://addyosmani.com/blog/intent-debt/</guid>
      </item>
    
      <item>
        <title>The Orchestration Tax</title>
        
        
          <description>Starting more agents is easy now. However, more agents running doesn&apos;t mean more of you available - your cognitive bandwidth doesn&apos;t parallelize. All the judgement to actually steer them and merge the code they write into the codebase still has to route through exactly one serial processor which is just you. Orchestration tax is basically the price you pay for forgetting this and the only real fix is to start architecting your own attention like you architect any concurrent system.</description>
        
        <pubDate>Sun, 24 May 2026 00:00:00 +0000</pubDate>
        <link>https://addyosmani.com/blog/orchestration-tax/</link>
        <guid isPermaLink="true">https://addyosmani.com/blog/orchestration-tax/</guid>
      </item>
    
      <item>
        <title>Don&apos;t Outsource the Learning</title>
        
        
          <description>Right now, it&apos;s too easy to let AI write the code while you skip the learning. The bug gets fixed. Your mental model doesn&apos;t move. We are silently trading future capability for present-day speed, and the tools won&apos;t force us to do otherwise. That part has to come from you.</description>
        
        <pubDate>Sat, 16 May 2026 00:00:00 +0000</pubDate>
        <link>https://addyosmani.com/blog/dont-outsource-learning/</link>
        <guid isPermaLink="true">https://addyosmani.com/blog/dont-outsource-learning/</guid>
      </item>
    
      <item>
        <title>Cognitive Surrender</title>
        
        
          <description>Cognitive offloading is delegating to the AI and still owning the answer. Cognitive surrender is when the AI&apos;s output quietly becomes your output and there is nothing left to check. For software engineers the line between the two moves under your feet most days, and most of us are crossing it without noticing.</description>
        
        <pubDate>Tue, 05 May 2026 00:00:00 +0000</pubDate>
        <link>https://addyosmani.com/blog/cognitive-surrender/</link>
        <guid isPermaLink="true">https://addyosmani.com/blog/cognitive-surrender/</guid>
      </item>
    
      <item>
        <title>Agent Skills</title>
        
        
          <description>AI coding agents take the shortest path to done, which usually means skipping the specs, tests, and reviews that make software reliable at scale. Agent Skills encodes those senior-engineer behaviors as workflows the agent has to follow, with anti-rationalization built in.</description>
        
        <pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate>
        <link>https://addyosmani.com/blog/agent-skills/</link>
        <guid isPermaLink="true">https://addyosmani.com/blog/agent-skills/</guid>
      </item>
    
  </channel>
</rss>