<story><title>Two Commits and the User Experience of Git</title><url>https://redfin.engineering/two-commits-that-wrecked-the-user-experience-of-git-f0075b77eab1</url></story><parent_chain></parent_chain><comment><author>michael_storm</author><text>&amp;gt; &lt;i&gt;Today, I specifically want to call attention to two commits by the lead maintainer of Git, Junio Hamano, that left the deepest scars.&lt;/i&gt;&lt;p&gt;Why call the maintainer out by name (and continually do so throughout the essay)? What purpose does that serve? To embarrass him for volunteering his time on an open source project that you&amp;#x27;ve built your business on, just because &lt;i&gt;you didn&amp;#x27;t like&lt;/i&gt; these two features he added? There was no personal behavior of his at play; he simply made some technical choices you disagree with.&lt;p&gt;Keep it technical, dude. This is ad-hominem and smug.</text></comment>
<story><title>Two Commits and the User Experience of Git</title><url>https://redfin.engineering/two-commits-that-wrecked-the-user-experience-of-git-f0075b77eab1</url></story><parent_chain></parent_chain><comment><author>ajarmst</author><text>&lt;i&gt;&amp;quot;It&amp;#x27;s like Unix!&amp;quot; people say. &amp;quot;rm doesn&amp;#x27;t warn you, either!&amp;quot;&lt;/i&gt;&lt;p&gt;Reminds me of one of my common complaints about that response.  The difference is that &amp;#x27;rm&amp;#x27; doesn&amp;#x27;t do anything but remove stuff---it removing things isn&amp;#x27;t surprising.  If a command has multiple potential effect types, and only some of them are destructive, then good UI would offer a warning.</text></comment>