<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Coding on Cdani&#39;s Blog</title>
    <link>https://c-daniele.github.io/en/tags/coding/</link>
    <description>Recent content in Coding on Cdani&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Mon, 18 May 2026 00:00:00 +0200</lastBuildDate>
    <atom:link href="https://c-daniele.github.io/en/tags/coding/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Claude Code, OpenCode, and π (pi): anatomy of a trivial request</title>
      <link>https://c-daniele.github.io/en/posts/2026-05-18-coding-harness-comparison/</link>
      <pubDate>Mon, 18 May 2026 00:00:00 +0200</pubDate>
      <guid>https://c-daniele.github.io/en/posts/2026-05-18-coding-harness-comparison/</guid>
      <description>&lt;h2 id=&#34;intro&#34;&gt;Intro&lt;/h2&gt;&#xA;&lt;p&gt;Anyone following the evolution of coding agents closely has probably heard about &lt;a href=&#34;https://pi.dev/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreffer &#34;&gt;pi&lt;/a&gt;, the minimalist harness that became popular in part because it is one of the components behind OpenClaw.&lt;/p&gt;&#xA;&lt;p&gt;One of the arguments in favor of pi&amp;rsquo;s minimalism is the contrast with the supposed &amp;ldquo;heaviness&amp;rdquo; of Claude Code, meaning an excessive use of tokens to carry out even trivial tasks. In that debate, pi and other harnesses built around the same philosophy are carving out some space.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Beyond vibe coding: a multi-agent pipeline for code conversion</title>
      <link>https://c-daniele.github.io/en/posts/2026-04-11-beyond-vibe-coding/</link>
      <pubDate>Sat, 11 Apr 2026 00:00:00 +0200</pubDate>
      <guid>https://c-daniele.github.io/en/posts/2026-04-11-beyond-vibe-coding/</guid>
      <description>&lt;h2 id=&#34;intro&#34;&gt;Intro&lt;/h2&gt;&#xA;&lt;p&gt;A few weeks ago I ran a very simple test: I took &lt;a href=&#34;https://github.com/msiemens/tinydb&#34; target=&#34;_blank&#34; rel=&#34;noopener noreffer &#34;&gt;TinyDB&lt;/a&gt;, opened a coding assistant, and asked it the most obvious thing in the world: &lt;em&gt;convert this to Rust&lt;/em&gt;.&lt;/p&gt;&#xA;&lt;p&gt;At first glance, the result did not even look that bad. The code looked plausible, it compiled, it passed a few tests, and it gave off that dangerous feeling of &amp;ldquo;I think we&amp;rsquo;re basically there.&amp;rdquo; But as soon as I started looking closely, the real problems surfaced: a deadlock in &lt;code&gt;insert_multiple&lt;/code&gt;, silent integer-to-float corruption in update operations, a panic path on invalid regex, and roughly 40% of the original package features simply gone.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Developer --&gt; Designer switch</title>
      <link>https://c-daniele.github.io/en/posts/2026-02-14-intro-spec-driven-development/</link>
      <pubDate>Sat, 14 Feb 2026 00:00:00 +0200</pubDate>
      <guid>https://c-daniele.github.io/en/posts/2026-02-14-intro-spec-driven-development/</guid>
      <description>&lt;h2 id=&#34;intro&#34;&gt;Intro&lt;/h2&gt;&#xA;&lt;p&gt;A few months ago I had to work on a complex application on AWS: a React frontend on Amplify, several Lambda functions, Bedrock with AgentCore, Knowledge Bases, and Prompt Management. I was in a hurry, and the temptation was overwhelming: open Claude Code, throw in a generic prompt, and hope it would &amp;ldquo;figure it out.&amp;rdquo; Instead, I did something different — I wrote specifications, reviewed them, spent an entire day on it — and that day it felt like I hadn&amp;rsquo;t accomplished anything. Two days later I had a working application. If I had improvised, I&amp;rsquo;d probably still be debugging.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
