<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Sina Siadat on Medium]]></title>
        <description><![CDATA[Stories by Sina Siadat on Medium]]></description>
        <link>https://medium.com/@siadat?source=rss-f2c7e648255c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*2QcIJ0tiRnw1Ev3AmwEN9Q.jpeg</url>
            <title>Stories by Sina Siadat on Medium</title>
            <link>https://medium.com/@siadat?source=rss-f2c7e648255c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 20:16:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@siadat/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Start commit messages with “I want to”]]></title>
            <link>https://medium.com/@siadat/start-commit-messages-with-i-want-to-aba7ae3ad77b?source=rss-f2c7e648255c------2</link>
            <guid isPermaLink="false">https://medium.com/p/aba7ae3ad77b</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[git]]></category>
            <dc:creator><![CDATA[Sina Siadat]]></dc:creator>
            <pubDate>Mon, 04 Jun 2018 15:54:48 GMT</pubDate>
            <atom:updated>2019-01-24T21:18:46.463Z</atom:updated>
            <content:encoded><![CDATA[<p>I want to suggest a more descriptive form of git commit messages.</p><p>A commit message written in the current prevalent dialect describes “what” has changed. However, the code itself is most often the best description of this “what”. A better commit message header describes the intention of the change. It should justify the necessity of this change in a high enough level target for its intended reviewer. It should answer the most important question asked by a reviewer, i.e., “why did you make this change?”, and not “what was changed in this commit?”</p><p>Starting a commit message with a phrase similar to“I want to” persuades the author to articulate their primary motivation. It shows what the author really intended to achieve in the change.</p><p>Let’s look at a familiar commit message:</p><blockquote>Register cleanupFuncs and invoke them onClose</blockquote><p>This message is merely rephrasing what is actually already available in the diff. Let’s rewrite this message indicating the primary motivation to answer the “why” instead:</p><blockquote>I want every part of the code to be responsible for their own cleanup methods</blockquote><p>This will make the commit head longer, but I think the benefits are worth the extra characters.</p><p>Starting a commit head with “I want to” helps other developers and reviewers form a holistic understanding of the change and make sense of it with less difficulty.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aba7ae3ad77b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>