<?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 Rahul Ahuja on Medium]]></title>
        <description><![CDATA[Stories by Rahul Ahuja on Medium]]></description>
        <link>https://medium.com/@rahulahuja404?source=rss-4ae45baabee7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ZCPuRbw0fW9O3umLZT9iJw.png</url>
            <title>Stories by Rahul Ahuja on Medium</title>
            <link>https://medium.com/@rahulahuja404?source=rss-4ae45baabee7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 21:04:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rahulahuja404/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[Things I wish I knew as a developer before collaborating]]></title>
            <link>https://medium.com/@rahulahuja404/things-i-wish-i-knew-as-a-developer-before-collaborating-278f86cbf94e?source=rss-4ae45baabee7------2</link>
            <guid isPermaLink="false">https://medium.com/p/278f86cbf94e</guid>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[beginner-developers]]></category>
            <dc:creator><![CDATA[Rahul Ahuja]]></dc:creator>
            <pubDate>Sat, 23 Feb 2019 20:45:07 GMT</pubDate>
            <atom:updated>2019-02-23T20:45:07.021Z</atom:updated>
            <content:encoded><![CDATA[<p>I remember how excited I used to get when me and my friends would start a new side project and plan our activities to collaborate over it.</p><p>“I will push the code by tomorrow 6:00”</p><p>Ah! The disappointment when Rohan would forget to do so. And amidst everything going on in the college, one would forget the entire plan we had devised to complete the thing in 2 weeks. We would still complete the side project but in 4 weeks instead of 2 with a lot of conflicts and dependencies upon each other. I have put up some of the things I wish I knew earlier to co-ordinate seamlessly.</p><p>1. How to use Trello</p><blockquote>Trello is a collaboration tool that organizes your projects into boards. In one glance, Trello tells you what’s being worked on, who’s working on what, and where something is in a process.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5rUPuECuBCz7h2T-wrU4sA.png" /><figcaption>Sample Trello Board.</figcaption></figure><p>Trello is a great tool to organise your tasks and track in which phase they are. I learnt proper use of Trello during my internship at <a href="https://www.gocomet.in/">GoComet</a>. The central idea behind using a board to track project activity is dividing the entire project into smaller, simpler parts which can be implemented by a single developer and then moving them across phases. A card represents a task in Trello and a list represents the phase it is in. Our Trello board usually consists of following</p><p><em>ToDo: </em>This list only contains all the tasks which are to be performed. Ensure that every card added to the ToDo list has a summary and a checklist which makes it easier to break the task into simpler actions. Assign the task to a person and add him to the card. If a more professional software is to be developed, add another member of team as a reviewer.</p><p><em>Doing: </em>When any member starts implementing a feature/task, he moves the card form <em>ToDo </em>to <em>Doing </em>list<em>. </em>As the actions required in the task are being completed, the checklist is checked. Once the entire checklist is complete, the developer will make a Pull Request of the task and move the card to <em>Tech Review.</em></p><p><em>Tech Review: </em>This is an optional phase which can be avoided if you are not developing a software for someone. A card in this list will contain the Pull Request link attached to it. It makes it easier for the reviewer to identify the PR under review. The reviewer reads the code and looks for code style checks and may question the logic.</p><p><em>Done: </em>Once the card/task has been reviewed, it is merged into master and moved to <em>Done.</em></p><p>2. Why Pull Request ?</p><p>Now that we created a card for every task and assigned a developer to it. To start contributing to the project, we would pull the master and create a new feature branch. We follow this convention for branch name</p><pre>  &lt;author&gt;/&lt;feature-name&gt;</pre><blockquote>The advantage of feature branching is that each developer can work on their own feature and be isolated from changes going on elsewhere. They can pull in changes from the mainline at their own pace, ensuring they don’t break the flow of their feature. Furthermore it allows the team to choose its features for release.</blockquote><p>3. Importance of Test Case</p><p>I am not going to write all the benefits of testing your software here. I only say that when collaborating with your friends, it may happen that something you wrote is modified by someone else and it can introduce bugs to your perfectly running piece of code. If you have written test cases, running them before committing the code ensures that such conditions do not arise.</p><p>Anyone who has developed software for more than 3 months will be aware of what testing actually is and not just the theoretical concept. Still almost everyone avoids writing test cases. Test cases are your safety net against buggy software. Delivering a buggy software to anyone even your friend is bad and why would you put your reputation as a developer on stake by being lazy.</p><p>Being a decent coder and capable of creating a software alone is one thing, but working in a team when you have just learnt software development and coordinating with them can be a headache at start. I hope the above list can help you better collaborate with your newly formed team.</p><p>References:</p><ul><li><a href="https://help.trello.com/article/708-what-is-trello">What is Trello? - Trello Help</a></li><li><a href="https://martinfowler.com/bliki/FeatureBranch.html">bliki: FeatureBranch</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=278f86cbf94e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>