<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Git on Arhuman's Blog</title><link>https://blog.assad.fr/en/tags/git/</link><description>Recent content in Git on Arhuman's Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 08 Sep 2026 12:00:00 +0700</lastBuildDate><atom:link href="https://blog.assad.fr/en/tags/git/index.xml" rel="self" type="application/rss+xml"/><item><title>Less is More: Why I Replaced Git with Jujutsu.</title><link>https://blog.assad.fr/en/post/jj_has_better_legs/</link><pubDate>Sun, 05 Apr 2026 02:38:37 +0100</pubDate><guid>https://blog.assad.fr/en/post/jj_has_better_legs/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;&#10;&lt;p&gt;In computing, the aphorism &amp;ldquo;Less is More&amp;rdquo; comes up often.&#10;With Jujutsu (jj), it takes a very concrete form: a simpler mental model can reduce the daily friction of version control.&lt;/p&gt;&#10;&lt;p&gt;In this article&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;, I will not try to &amp;ldquo;prove&amp;rdquo; that &lt;code&gt;jj&lt;/code&gt; is superior to &lt;code&gt;git&lt;/code&gt;. I will show, on a concrete case, why some common operations: interrupting work in progress, reorganizing changes, fixing a non-atomic commit or resolving a conflict, become more natural with jj.&lt;/p&gt;</description></item></channel></rss>