<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Open-Source on Nitzan's Blog</title><link>https://blog.nitzan.fyi/tags/open-source/</link><description>Recent content in Open-Source on Nitzan's Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 21 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.nitzan.fyi/tags/open-source/index.xml" rel="self" type="application/rss+xml"/><item><title>Introducing Maple: Visual Review Written by People, Fixed by Agents</title><link>https://blog.nitzan.fyi/posts/introducing-maple/</link><pubDate>Mon, 21 Sep 2026 00:00:00 +0000</pubDate><guid>https://blog.nitzan.fyi/posts/introducing-maple/</guid><description>&lt;blockquote&gt;
&lt;p&gt;A coding agent can fix almost anything you hand it — as long as what you handed it is clear and actionable. A visual review comment usually isn&amp;rsquo;t.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Here&amp;rsquo;s the loop I got tired of.&lt;/p&gt;
&lt;p&gt;Someone opens a preview deployment — a designer, a product manager, whoever has the link — and something is wrong. They screenshot it, drop it in Slack, and write &lt;em&gt;&amp;ldquo;the spacing under the chart looks off on the dashboard&amp;rdquo;&lt;/em&gt;. Now the work starts: I read the message, open the preview, guess which of four nearly-identical cards they meant, grep for the component, and only then make a two-line change.&lt;/p&gt;</description></item></channel></rss>