<?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: Rick Leffke</title>
    <description>The latest articles on DEV Community by Rick Leffke (@rick_leffke_6541e28129e2a).</description>
    <link>https://dev.to/rick_leffke_6541e28129e2a</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%2F4220764%2F1da3271a-bec6-4f0d-80be-18cfba5f9320.png</url>
      <title>DEV Community: Rick Leffke</title>
      <link>https://dev.to/rick_leffke_6541e28129e2a</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rick_leffke_6541e28129e2a"/>
    <language>en</language>
    <item>
      <title>The Coding Agent Your Developer Uses Matters More Than the Demo</title>
      <dc:creator>Rick Leffke</dc:creator>
      <pubDate>Fri, 06 Nov 2026 19:09:59 +0000</pubDate>
      <link>https://dev.to/rick_leffke_6541e28129e2a/the-coding-agent-your-developer-uses-matters-more-than-the-demo-5g0p</link>
      <guid>https://dev.to/rick_leffke_6541e28129e2a/the-coding-agent-your-developer-uses-matters-more-than-the-demo-5g0p</guid>
      <description>&lt;p&gt;Most business owners I talk to judge an AI project by the demo. The agent answers a question. It drafts an email. It looks finished.&lt;/p&gt;

&lt;p&gt;What rarely comes up is the quieter choice underneath: which coding agent is your developer working in while they build that for you?&lt;/p&gt;

&lt;p&gt;Full disclosure: I built Agent Ready Rankings (&lt;a href="https://rankings.leffke.com" rel="noopener noreferrer"&gt;https://rankings.leffke.com&lt;/a&gt;), a site that scores AI agent tools out of 10. I track six coding agents there. The scores below are overall scores from my Nov 5 data run — not a same-day refresh — and browsing the site is free. The full score breakdown is part of Pro, $10/month.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why the coding agent matters to an owner
&lt;/h2&gt;

&lt;p&gt;A coding agent is the AI-assisted editor or CLI your builder uses to write, change, and ship software. It is not the customer-facing agent you may be buying. It is the tool that shapes how fast fixes land, how expensive iteration is, and how transferable the work is if your developer leaves or you hire someone else.&lt;/p&gt;

&lt;p&gt;If the stack is obscure, stale, or locked to one person's setup, you inherit that risk.&lt;/p&gt;

&lt;h2&gt;
  
  
  The tools I track (overall scores)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Cursor: 8.45 out of 10.&lt;/strong&gt; Highest in this group. AI-native code editor with agent mode and strong multi-file edits. Freemium. Last release I've recorded: October 20, 2026 (last checked October 29).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Claude Code: 8.4 out of 10.&lt;/strong&gt; Anthropic's agentic coding tool for terminal-native, repo-wide work. Usage-based pricing. Last release I've tracked: November 3, 2026.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Windsurf: 8.05 out of 10.&lt;/strong&gt; Agentic IDE (Cascade-style multi-step flows). Freemium. Last release I've tracked: October 30, 2026.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;GitHub Copilot: 7.4 out of 10.&lt;/strong&gt; Widely adopted IDE copilot with deep GitHub and VS Code integration. Paid. Changelog activity I've tracked through November 4, 2026.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Aider: 7.3 out of 10.&lt;/strong&gt; Open-source terminal pair programmer with strong git integration. Free (you bring model API costs). Last release I've seen: August 9, 2025 — so ask how your builder plans to stay current before you standardize on it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Continue: 6.7 out of 10.&lt;/strong&gt; Open-source IDE autopilot where you bring your own models. Free. Last release I've recorded: June 18, 2026 — worth confirming maintenance before you depend on it.&lt;/p&gt;

&lt;h2&gt;
  
  
  A simple owner checklist
&lt;/h2&gt;

&lt;p&gt;Before you approve the next phase of AI build work, ask:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Which coding agent does the team actually use day to day?&lt;/li&gt;
&lt;li&gt;Is that tool still shipping updates on a pace you're comfortable with?&lt;/li&gt;
&lt;li&gt;Could another developer open the same project next month without a week of reverse-engineering?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You do not need to become an engineer to ask those questions. You do need answers before the demo turns into a long-term dependency.&lt;/p&gt;

&lt;h2&gt;
  
  
  About the rankings
&lt;/h2&gt;

&lt;p&gt;Agent Ready Rankings covers 22 AI agent tools across coding agents, LLM APIs, agent frameworks, voice, memory, and evaluation and safety. I built it. Treat every score as one informed opinion and tell me where you think I'm off.&lt;/p&gt;

&lt;p&gt;Coding agents category: &lt;a href="https://rankings.leffke.com/categories/coding-agents" rel="noopener noreferrer"&gt;https://rankings.leffke.com/categories/coding-agents&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>coding</category>
      <category>agents</category>
      <category>productivity</category>
    </item>
    <item>
      <title>How to Know Your AI Agent Is Doing the Right Job After Launch</title>
      <dc:creator>Rick Leffke</dc:creator>
      <pubDate>Wed, 04 Nov 2026 13:58:54 +0000</pubDate>
      <link>https://dev.to/rick_leffke_6541e28129e2a/how-to-know-your-ai-agent-is-doing-the-right-job-after-launch-285j</link>
      <guid>https://dev.to/rick_leffke_6541e28129e2a/how-to-know-your-ai-agent-is-doing-the-right-job-after-launch-285j</guid>
      <description>&lt;p&gt;Most AI agent pilots I see go well in the demo. The trouble starts a few weeks after launch, when the agent is answering real customers, reading real documents, and nobody is watching closely anymore.&lt;/p&gt;

&lt;p&gt;So the question I now ask every business owner before an agent goes live is simple: how will you know when it gets something wrong?&lt;/p&gt;

&lt;p&gt;Full disclosure: I built Agent Ready Rankings (&lt;a href="https://rankings.leffke.com" rel="noopener noreferrer"&gt;https://rankings.leffke.com&lt;/a&gt;), a site that scores AI agent tools out of 10. Here's what the monitoring and evaluation corner of it looks like today, and how I'd think about it as an owner rather than an engineer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why monitoring is a business decision, not just a technical one
&lt;/h2&gt;

&lt;p&gt;An agent that drafts emails, answers support questions, or pulls numbers from your files makes decisions on your behalf. When it's wrong, the cost lands on you: a bad answer to a customer, a wrong figure in a quote, a private detail shared where it shouldn't be.&lt;/p&gt;

&lt;p&gt;Monitoring tools give you three things: a record of what the agent did, a way to test it against known good answers, and an early warning when quality slips. Without them, you find out about problems from your customers.&lt;/p&gt;

&lt;h2&gt;
  
  
  The tools I track
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;LangSmith: 7.1 out of 10.&lt;/strong&gt; The highest-scoring tool in this group. It handles tracing (seeing each step an agent took), evaluation, and deployment for agents built with LangChain and LangGraph. It's mature enough to trust in production. Its latest changelog I've ingested covers October 19 to 26. It has a free tier with paid plans.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Arize Phoenix: 6.75 out of 10.&lt;/strong&gt; Open-source observability and evaluation for traces and LLM apps, with a paid option. It's moving fast: version 21.0.0, a major release, shipped on October 29. A good fit if you want to keep data on your own servers.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Ragas: 5.2 out of 10.&lt;/strong&gt; A free evaluation library focused on checking the quality of answers drawn from your documents. Useful and free, but its last release I've seen was January 13, 2026, so it's one to watch. Confirm it's still actively maintained before you build a process around it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which fits which business
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;You built your agent with LangChain or LangGraph:&lt;/strong&gt; start with LangSmith. It plugs in with the least effort.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You need data to stay in-house, or you want to avoid lock-in:&lt;/strong&gt; look at Arize Phoenix and its self-hosted option.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You mainly need to check answers from your own documents and have someone technical:&lt;/strong&gt; Ragas can work as a free starting point, with the maintenance caveat above.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A simple rule before launch
&lt;/h2&gt;

&lt;p&gt;Don't put an agent in front of customers until someone on your team can answer three questions from a dashboard: what did it do, why did it do it, and how often is it right? If you can't answer those, you're not ready to scale it, no matter how good the demo looked.&lt;/p&gt;

&lt;h2&gt;
  
  
  About the rankings
&lt;/h2&gt;

&lt;p&gt;Agent Ready Rankings scores 22 AI agent tools across coding agents, LLM APIs, agent frameworks, voice, memory, and evaluation and safety, with release dates checked as new versions come out. Browsing is free. The full score breakdown for each tool is part of Pro, $10/month.&lt;/p&gt;

&lt;p&gt;See the evaluation and safety category here: &lt;a href="https://rankings.leffke.com/categories/eval-safety" rel="noopener noreferrer"&gt;https://rankings.leffke.com/categories/eval-safety&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I'd like to hear how you handle this. If you have an agent in production, what do you use to catch its mistakes?&lt;/p&gt;

</description>
      <category>ai</category>
      <category>agents</category>
      <category>llm</category>
      <category>observability</category>
    </item>
    <item>
      <title>Helping Companies Adopt AI Agents Safely</title>
      <dc:creator>Rick Leffke</dc:creator>
      <pubDate>Sun, 01 Nov 2026 15:37:16 +0000</pubDate>
      <link>https://dev.to/rick_leffke_6541e28129e2a/hi-dev-im-rick-helping-companies-adopt-ai-agents-safely-4en0</link>
      <guid>https://dev.to/rick_leffke_6541e28129e2a/hi-dev-im-rick-helping-companies-adopt-ai-agents-safely-4en0</guid>
      <description>&lt;p&gt;I'm Rick Leffke, CEO of Agent Ready, an agentic AI business that helps companies adopt AI agents safely and effectively. We do training, pilot projects, safety checks, and brand/bot risk work.&lt;/p&gt;

&lt;p&gt;I also run &lt;a href="https://rankings.leffke.com" rel="noopener noreferrer"&gt;Agent Ready Rankings&lt;/a&gt;, daily rankings of AI agent tools, from coding assistants to voice AI. We score each tool on recent releases and how well it works for real business use. Cursor has held the top spot at 8.75 since the Oct 29 update.&lt;/p&gt;

&lt;p&gt;Take a look at &lt;a href="https://rankings.leffke.com" rel="noopener noreferrer"&gt;https://rankings.leffke.com&lt;/a&gt; and tell me which tools you think I'm missing.&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
