<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ai on Quentin Rousseau</title><link>http://blog.quent.in/tags/ai/</link><description>Recent content in Ai on Quentin Rousseau</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 19 May 2026 08:00:00 +0000</lastBuildDate><atom:link href="http://blog.quent.in/tags/ai/index.xml" rel="self" type="application/rss+xml"/><item><title>Your Small PR Rule Won't Survive AI</title><link>http://blog.quent.in/blog/2026/05/19/your-small-pr-rule-wont-survive-ai/</link><pubDate>Tue, 19 May 2026 08:00:00 +0000</pubDate><guid>http://blog.quent.in/blog/2026/05/19/your-small-pr-rule-wont-survive-ai/</guid><description>&lt;p&gt;For two years, we enforced a strict small-PR culture at &lt;a href="https://rootly.com"target="_blank"
 class="inline-flex items-center gap-1"
&gt;Rootly&lt;svg class="h-3 w-3 flex-shrink-0" id="external-link" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"&gt;&lt;path fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M15 3h6v6m-11 5L21 3m-3 10v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6"/&gt;&lt;/svg&gt;
&lt;/a&gt;. Stacked PRs, atomic changes, never more than a couple hundred lines. The logic was sound: smaller diffs are easier to review, easier to revert, easier to reason about.&lt;/p&gt;
&lt;p&gt;Then AI started writing most of our code.&lt;/p&gt;</description></item><item><title>Two Mornings a Day</title><link>http://blog.quent.in/blog/2026/04/08/two-mornings-a-day/</link><pubDate>Wed, 08 Apr 2026 08:00:00 +0000</pubDate><guid>http://blog.quent.in/blog/2026/04/08/two-mornings-a-day/</guid><description>&lt;p&gt;I haven&amp;rsquo;t slept a normal night in over four years. Somehow, I feel better than I used to.&lt;/p&gt;
&lt;p&gt;When I started &lt;a href="https://rootly.com"target="_blank"
 class="inline-flex items-center gap-1"
&gt;Rootly&lt;svg class="h-3 w-3 flex-shrink-0" id="external-link" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"&gt;&lt;path fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M15 3h6v6m-11 5L21 3m-3 10v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6"/&gt;&lt;/svg&gt;
&lt;/a&gt;, my sleep broke. US customers needed me in the morning. Features needed shipping at night. My brain refused to stop planning in between. I wasn&amp;rsquo;t grinding on purpose. I was building a company across time zones, and my body just&amp;hellip; adjusted.&lt;/p&gt;</description></item><item><title>Watts, Water, and Carbon: What Your AI Prompts Actually Cost</title><link>http://blog.quent.in/blog/2026/03/19/watts-water-and-carbon-what-your-ai-prompts-actually-cost/</link><pubDate>Thu, 19 Mar 2026 12:00:00 +0000</pubDate><guid>http://blog.quent.in/blog/2026/03/19/watts-water-and-carbon-what-your-ai-prompts-actually-cost/</guid><description>&lt;p&gt;Every time you ask an AI to summarize a document, generate an image, or write code, a GPU somewhere lights up — and a power meter ticks upward. As someone who runs AI agents all day, I started wondering: what&amp;rsquo;s the actual energy footprint of this revolution I&amp;rsquo;m participating in?&lt;/p&gt;
&lt;p&gt;The answer is more nuanced than the headlines suggest.&lt;/p&gt;
&lt;h2 id="what-a-single-prompt-actually-costs"&gt;What a single prompt actually costs&lt;/h2&gt;
&lt;p&gt;Let&amp;rsquo;s start small. You&amp;rsquo;ve probably seen the stat that a ChatGPT query uses &amp;ldquo;10x more energy than a Google search.&amp;rdquo; &lt;a href="https://technical.ly/civics/chatgpt-vs-google-energy-use/"target="_blank"
 class="inline-flex items-center gap-1"
&gt;The reality is more complicated&lt;svg class="h-3 w-3 flex-shrink-0" id="external-link" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"&gt;&lt;path fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M15 3h6v6m-11 5L21 3m-3 10v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6"/&gt;&lt;/svg&gt;
&lt;/a&gt;. Google&amp;rsquo;s traditional search uses about &lt;strong&gt;0.3 watt-hours&lt;/strong&gt;. The Electric Power Research Institute estimated a ChatGPT request at &lt;strong&gt;2.9 Wh&lt;/strong&gt; — roughly 10x.&lt;/p&gt;</description></item><item><title>One More Prompt: The Dopamine Trap of Agentic Coding</title><link>http://blog.quent.in/blog/2026/03/09/one-more-prompt-the-dopamine-trap-of-agentic-coding/</link><pubDate>Mon, 09 Mar 2026 14:00:00 +0000</pubDate><guid>http://blog.quent.in/blog/2026/03/09/one-more-prompt-the-dopamine-trap-of-agentic-coding/</guid><description>&lt;p&gt;It&amp;rsquo;s 2:47 AM on a Tuesday. I&amp;rsquo;m not debugging a production outage. There&amp;rsquo;s no deadline. I&amp;rsquo;m just watching Claude Code refactor a module — and I can&amp;rsquo;t stop. One more prompt. One more agent run. One more hit.&lt;/p&gt;
&lt;p&gt;If this sounds familiar, you&amp;rsquo;re not alone. Something strange is happening to developers in 2026: &lt;strong&gt;AI coding tools may be triggering the same dopamine loops as slot machines&lt;/strong&gt;, and the tech industry is sleepwalking into it.&lt;/p&gt;</description></item><item><title>From Writing Code to Orchestrating Agents</title><link>http://blog.quent.in/blog/2026/03/09/from-vs-code-to-agent-orchestrators-how-multi-agent-workflows-changed-everything/</link><pubDate>Mon, 09 Mar 2026 08:47:29 +0000</pubDate><guid>http://blog.quent.in/blog/2026/03/09/from-vs-code-to-agent-orchestrators-how-multi-agent-workflows-changed-everything/</guid><description>&lt;p&gt;My dev workflow has changed more in early 2026 than in the previous five years. I went from writing code in VS Code, to pair-programming with AI in Cursor, to running CLI agents like Claude Code and Codex — and now I&amp;rsquo;m orchestrating multiple agents working in parallel on different tasks at the same time.&lt;/p&gt;
&lt;p&gt;Each step felt like a leap. But the jump to multi-agent orchestration is the one that fundamentally changed how I think about shipping software.&lt;/p&gt;</description></item><item><title>Your AI Agent Doesn’t Need an MCP Server — It Needs a Good CLI</title><link>http://blog.quent.in/blog/2026/02/24/your-ai-agent-doesnt-need-an-mcp-server-it-needs-a-good-cli/</link><pubDate>Tue, 24 Feb 2026 23:27:05 +0000</pubDate><guid>http://blog.quent.in/blog/2026/02/24/your-ai-agent-doesnt-need-an-mcp-server-it-needs-a-good-cli/</guid><description>&lt;p&gt;Every week, a new MCP server shows up on GitHub that wraps a CLI tool that already existed. MCP server for GitHub? &lt;code&gt;gh&lt;/code&gt; has been doing that since 2020. MCP server for AWS? The &lt;code&gt;aws&lt;/code&gt; CLI covers 200+ services with &lt;code&gt;--output json&lt;/code&gt;. MCP server for Datadog? They shipped a CLI instead — and it works better.&lt;/p&gt;
&lt;p&gt;I get the excitement around &lt;a href="https://modelcontextprotocol.io/"target="_blank"
 class="inline-flex items-center gap-1"
&gt;MCP&lt;svg class="h-3 w-3 flex-shrink-0" id="external-link" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"&gt;&lt;path fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M15 3h6v6m-11 5L21 3m-3 10v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6"/&gt;&lt;/svg&gt;
&lt;/a&gt; (Model Context Protocol). It&amp;rsquo;s a clean standard for connecting AI to external systems. Anthropic designed it well. But somewhere along the way, the community started treating MCP as the &lt;em&gt;default&lt;/em&gt; way to give AI agents access to tools — even when a perfectly good CLI already exists.&lt;/p&gt;</description></item><item><title>From "Maintainers Wanted" to Three Major Releases in a Weekend</title><link>http://blog.quent.in/blog/2026/02/24/from-maintainers-wanted-to-three-major-releases-in-a-weekend/</link><pubDate>Tue, 24 Feb 2026 22:42:22 +0000</pubDate><guid>http://blog.quent.in/blog/2026/02/24/from-maintainers-wanted-to-three-major-releases-in-a-weekend/</guid><description>&lt;p&gt;I have 50+ public repositories on GitHub. Some of them haven&amp;rsquo;t been touched in years. A few still get stars and forks weekly. Most sit somewhere in between — not abandoned, not active, just&amp;hellip; there.&lt;/p&gt;
&lt;p&gt;Until recently, that &amp;ldquo;just there&amp;rdquo; state came with guilt. Every Dependabot PR I didn&amp;rsquo;t merge, every issue I didn&amp;rsquo;t respond to, every README that still referenced a deprecated API — it all felt like debt accumulating. Maintaining open-source repositories was a second job I never signed up for.&lt;/p&gt;</description></item><item><title>Rethinking How We Evaluate Product Engineers in the AI Era</title><link>http://blog.quent.in/blog/2026/02/18/rethinking-how-we-evaluate-product-engineers-in-the-ai-era/</link><pubDate>Wed, 18 Feb 2026 12:24:08 +0000</pubDate><guid>http://blog.quent.in/blog/2026/02/18/rethinking-how-we-evaluate-product-engineers-in-the-ai-era/</guid><description>&lt;p&gt;Over the past few years as CTO at &lt;a href="https://rootly.com"target="_blank"
 class="inline-flex items-center gap-1"
&gt;Rootly&lt;svg class="h-3 w-3 flex-shrink-0" id="external-link" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"&gt;&lt;path fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M15 3h6v6m-11 5L21 3m-3 10v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6"/&gt;&lt;/svg&gt;
&lt;/a&gt;, I&amp;rsquo;ve had to fundamentally rethink how we evaluate product engineers. The skills that used to separate great candidates from good ones have shifted — not because the bar is lower, but because AI has changed what &amp;ldquo;doing the work&amp;rdquo; actually looks like.&lt;/p&gt;</description></item><item><title>Back Online: From Octopress to Hugo, From Silence to AI</title><link>http://blog.quent.in/blog/2026/02/17/back-online-from-octopress-to-hugo-from-silence-to-ai/</link><pubDate>Tue, 17 Feb 2026 23:32:48 +0000</pubDate><guid>http://blog.quent.in/blog/2026/02/17/back-online-from-octopress-to-hugo-from-silence-to-ai/</guid><description>&lt;p&gt;My last blog post was in February 2017. Nine years ago.&lt;/p&gt;
&lt;p&gt;It wasn&amp;rsquo;t intentional. I didn&amp;rsquo;t wake up one day and decide to stop writing. I just&amp;hellip; didn&amp;rsquo;t start the next post. Then a month passed, then a year, then almost a decade. The classic &lt;code&gt;// TODO: write blog post&lt;/code&gt; that never gets resolved.&lt;/p&gt;
&lt;h2 id="what-happened"&gt;What happened&lt;/h2&gt;
&lt;p&gt;Life happened — and it was a busy one.&lt;/p&gt;
&lt;p&gt;When I wrote that last post about &lt;a href="http://blog.quent.in/blog/2017/02/06/pgbouncerhero-dashboard-for-your-pgbouncers/"&gt;PgBouncerHero&lt;/a&gt; in 2017, I was at &lt;a href="https://www.instacart.com/"target="_blank"
 class="inline-flex items-center gap-1"
&gt;Instacart&lt;svg class="h-3 w-3 flex-shrink-0" id="external-link" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"&gt;&lt;path fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M15 3h6v6m-11 5L21 3m-3 10v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6"/&gt;&lt;/svg&gt;
&lt;/a&gt; as one of their early SREs, building the infrastructure that took the platform from thousands of orders a week to millions.&lt;/p&gt;</description></item></channel></rss>