<?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 Saurabh Anand on Medium]]></title>
        <description><![CDATA[Stories by Saurabh Anand on Medium]]></description>
        <link>https://medium.com/@sawrubh?source=rss-b9da25e89b6f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*is7LhBrySL_FSn62.jpeg</url>
            <title>Stories by Saurabh Anand on Medium</title>
            <link>https://medium.com/@sawrubh?source=rss-b9da25e89b6f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:29:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sawrubh/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[Tips and Tricks For Fixing Your First Bug]]></title>
            <link>https://medium.com/@sawrubh/tips-and-tricks-for-fixing-your-first-bug-f1063973df01?source=rss-b9da25e89b6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f1063973df01</guid>
            <dc:creator><![CDATA[Saurabh Anand]]></dc:creator>
            <pubDate>Sun, 12 Oct 2014 03:32:40 GMT</pubDate>
            <atom:updated>2014-10-12T03:33:21.733Z</atom:updated>
            <content:encoded><![CDATA[<p>I have come across a lot of contributors who have tried to fix their first bug but had gotten stuck at various stages of the process. So here are some of the tips and tricks I used to be able to fix bugs when I started.</p><p><strong>Your first point of contact: IRC</strong></p><ul><li>First of all, don’t be afraid or embarrassed to ask your questions. When I started I had the feeling what I used to ask was really stupid, but if you’ve tried finding the answer for some time and haven’t yet found it, it’s certainly NOT trivial so please ask your questions. I have wasted quite some time and been stuck for days just because of not asking for help. Trust me, we’re really sweet folks and love to answer questions ☺</li><li>Once you decide to ask the question, go ahead and ask it. Don’t just say hi and wait for someone to reply to you and only then will you ask your question. Also ask the question directly instead of asking whether people would be able to answer, we won’t know if we’ll be able to unless you ask it right? Basically <strong>don’t ask to ask your questions.</strong></li><li>Be patient. People on the IRC channels are mostly from different timezones so everyone might not be awake when you post your questions.</li><li>Extending the first point, use persistent IRC clients, like <a href="https://irccloud.com/">IRCCloud</a> or <a href="https://www.waartaa.com/">Waartaa</a> so you don’t miss the answers which people give when you sleep. Or you could just check the <a href="http://logbot.glob.com.au/?c=mozilla%23introduction">IRC logs</a> later.</li><li>Try and read the instructions in the topic that we have, like on #introduction we have links to <a href="http://whatcanidoformozilla.org/">What Can I Do For Mozilla</a> and <a href="http://www.joshmatthews.net/bugsahoy/">BugsAhoy</a> which are great resources to find bugs and projects to work on.</li><li>Comment on the bug stating your interest to work on it, try and find the person listed as the mentor there on IRC and ping him or just tell us on #introduction so that we can find him/her for you.</li></ul><p><strong>Let’s get building</strong></p><ul><li>When you’re having issues with building the project, <a href="https://pastebin.mozilla.org/">pastebin</a> the exact output you get so that we can more information to find out the reason and help you. Similarly when you’re writing a patch and it’s not working, <a href="https://pastebin.mozilla.org/">pastebin</a> the code instead of simply stating that you’re working on something and it’s not working, so that we might be able to spot a silly mistake you might be overlooking, if that might be the case. This last part has been stressed a lot by the people I’m working with in #instantbird and I think it’s a great tip. You could also use |./mach pastebin| after you get a build error.</li></ul><p><strong>Where is da code</strong></p><ul><li>We try to mention the relevant code for fixing the bug in the comments or it might be inferred from the component the bug is filed in. If it isn’t clear, I follow the steps Josh mentioned so beautifully in his <a href="http://www.joshmatthews.net/blog/2012/01/answering-questions/">blog post</a>.</li></ul><p><strong>Gimme moar</strong></p><ul><li>If you’re looking to do long term contribution, what worked for me was finding a project or a feature being worked upon and having some bite-sized dependency bugs which I could fix. That way, I felt responsible for the implementation of the project, I had a sense of accomplishment and progress when I fixed each dependency and also I didn’t have the overhead of jumping between very different parts of the code which improved my efficiency.</li></ul><p>If you want more detailed tips, feel free to checkout an <a href="http://inpursuitoflaziness.blogspot.in/2014/02/getting-started-with-bug-squashing.html">excellent post</a> by Manish.</p><p>These are my tips, do you have some more in mind? Feel free to comment here, email me or share them with me on <a href="https://twitter.com/sawrubh">twitter</a>.</p><p><em>Originally published at </em><a href="http://sawrubh.tumblr.com/post/89737523167/tips-and-tricks-for-fixing-your-first-bug"><em>sawrubh.tumblr.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f1063973df01" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BugStrips: Bitstrips but about Bugs and with cute Dinos]]></title>
            <link>https://medium.com/@sawrubh/bugstrips-bitstrips-but-about-bugs-and-with-cute-dinos-d626535c4dd6?source=rss-b9da25e89b6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d626535c4dd6</guid>
            <dc:creator><![CDATA[Saurabh Anand]]></dc:creator>
            <pubDate>Sun, 12 Oct 2014 03:31:13 GMT</pubDate>
            <atom:updated>2014-10-12T03:31:13.403Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>The problem</strong></p><p>The problem I recently noticed was that my work related to Mozilla was so specific that I couldn’t share it with my non-technical friends even though my work might be something they ended up using (like the Per-Window Private Browsing feature in Firefox). So I needed a way to share what I’m working on or what I’ve worked on, easily and in a fun manner, which appeals to both my technical and specially my non-technical friends.</p><p><strong>The possible solution</strong></p><p>BugStrips, bitstrips but about bugs and with cute dinos. <a href="http://www.bitstrips.com/">Bitstrips</a> as some of you might know and/or have used, is this quite popular means of sharing a comic about your friends and you, using these hilarious illustrations showing various scenes you might have yourself into, like eating a pizza, or watching World Cup.</p><p>The idea of bugstrips is instead to share what bugs or features you’re working on, on the social networks of your choice and having little cheeky, funny dialogues between characters. Right now, I think the dialogue between the kid and the dino (like in <a href="https://assets.mozillalabs.com/Graphics/Wallpapers/Mozilla-is-my-Dinosaur/mozilla-dinosaur_wallpaper_2560x1440.jpg">Sean Martell’s art</a>) would be awesome. The costume of the dino and/or the kid, the background and other things could be customized based on the bug we’re talking about. For example when we’re talking about privacy, the dino might be wearing a <a href="http://en.wikipedia.org/wiki/Domino_mask">Domino mask</a> or when we’re talking about freedom, the dino and the kid could be flying, something like that.</p><p>Advantages of such a project</p><ul><li><em>Brand Awareness</em>: We will be able to increase awareness about the new features we implement or bugs which new contributors help fix.</li><li><em>On boarding of new contributors</em>: There might be people who find out about Mozilla, Open Source and it’s projects, in the social networks that these strips are shared in and eventually end up as contributors.</li><li><em>Contributor recognition</em>: Appreciation is an important factor, I believe in sustained contribution. We try and appreciate, recognize the efforts of volunteers. If this appreciation comes from the contributors own circles, that would be even more great. I personally feel delighted every time someone likes something I post (I know what you think about me now ;) ) and I think others do too so this might appeal to them.</li></ul><p>Things to keep in mind</p><ul><li>The art should be good.</li><li>The text should be cheeky, hilarious, fun, anything which has appeal, like for example we have on <a href="http://whatcanidoformozilla.org/">What Can I Do For Mozilla</a>.</li></ul><p>In the User Centered Design session at MozCamp, <a href="https://twitter.com/habber">Holly</a> told us to define the audience and success metrics for such a project.</p><p>Audience</p><ul><li>Developers who would use this to share BugStrips to their social networks.</li><li>People who would view the BugStrips on the social networks.</li></ul><p>Success Metrics</p><ul><li>Developers keeps fixing bugs or fixed more bugs because of this.</li><li>Number of views or clicks or comments on these strips.</li><li>Number of people who end up on our getting started resources or BugZilla because of these strips.</li></ul><p><strong>Implementation Details</strong></p><p>It makes sense to implement this as a separate site where you could see the list of bugs you’ve fixed and the bugs you’re currently working on, instead of trying to integrate it into BugZilla in the first go.</p><p><strong>UX Prototype</strong></p><p>Here’s a really raw UX prototype of how the entire thing would flow: <a href="http://imgur.com/ANcw8Te">Click Me</a>!</p><p><strong>Appendix</strong></p><ul><li>Cute Dinos: I really love Sean Martell’s <a href="http://thewebrocks.com/dinocards/#dino1">art</a>, specially his <a href="http://blog.seanmartell.com/2013/09/17/mozilla-is-my-dinosaur/">dinos</a>. (You can download a wallpaper of these <a href="https://assets.mozillalabs.com/Graphics/Wallpapers/Mozilla-is-my-Dinosaur/">here</a>).</li><li>Awesome Art: You can make something so interesting as <a href="https://bugzilla.mozilla.org/">BugZilla</a>, moar interesting by such <a href="https://twitter.com/ibarlow/status/459079399376035840">beautiful art</a>. Other <a href="http://blog.seanmartell.com/2013/03/22/so-you-want-to-sketch-a-hero/">such</a> <a href="http://blog.seanmartell.com/brands/">beautiful</a> art are always an inspiration.</li></ul><p><strong>Acknowledgement</strong></p><p>My brother for pointing out that he didn’t understand what I was working on all this time. Larissa for brainstorming on this idea with me during MozCamp’s UCD session. Holly for teaching us the framework on which to evaluate and think about ideas/apps/products.</p><p>Got any feedback, suggestions, snide remarks? Feel free to comment here, email me or let me know on <a href="https://twitter.com/sawrubh">twitter</a>. Now let’s build this thing, shall we?</p><p><em>Originally published at </em><a href="http://sawrubh.tumblr.com/post/90274223062/bugstrips-bitstrips-but-about-bugs-and-with-cute-dinos"><em>sawrubh.tumblr.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d626535c4dd6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>