<?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 Amy Graham on Medium]]></title>
        <description><![CDATA[Stories by Amy Graham on Medium]]></description>
        <link>https://medium.com/@amyygraham?source=rss-f27933f4ffa1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*DrhE14gsYGqbjiAYpIlTZQ.jpeg</url>
            <title>Stories by Amy Graham on Medium</title>
            <link>https://medium.com/@amyygraham?source=rss-f27933f4ffa1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 20:58:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@amyygraham/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[Open source is easy]]></title>
            <link>https://medium.com/sainsburys-engineering/open-source-is-easy-8e4771c4b427?source=rss-f27933f4ffa1------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e4771c4b427</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[pandas]]></category>
            <category><![CDATA[contribution]]></category>
            <dc:creator><![CDATA[Amy Graham]]></dc:creator>
            <pubDate>Wed, 15 Jul 2020 07:47:18 GMT</pubDate>
            <atom:updated>2020-07-15T07:47:18.720Z</atom:updated>
            <content:encoded><![CDATA[<p>A guide on how to contribute and why you should</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UvyfVrgwAbl6IcTcgEoO9A.jpeg" /><figcaption>Credit to <a href="https://unsplash.com/">https://unsplash.com</a></figcaption></figure><p>Contributing to open source projects may seem daunting at first, however, if I can do it (a complete novice), then anybody can.</p><p>I left university with a Philosophy degree and a whole lot of existential angst, but upon introspection I decided to put my analytical skills to use and pursue a career in data engineering. Following 4 months of training at <a href="https://kubrickgroup.com/">Kubrick Group</a>, I now work at <a href="https://sainsburys.jobs/roles/digital-tech-data/">Sainsbury’s</a> as a Data Engineer where I decided to use my 10% development time to make my first contribution to open source — so yes, <em>anybody </em>can do it.</p><p>This article should persuade you that no matter how little or how much experience you have, there are a multitude of benefits that you can reap as a developer. The team I work in comprises of a mix of engineers, from junior devs to experienced programmers, yet every single one of us has obtained varying benefits from contributing to open source. And if you’re still wondering whether it really is that simple, I will demonstrate with a step-by-step example of a contribution to <a href="https://github.com/pandas-dev/pandas">pandas</a> (data analysis package for Python). Feel free to skip to the <a href="#d71b">step-by-step</a><strong> </strong>if you are ready to get stuck in.</p><h3>What’s in it for me?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FCItoYOS9cwwlxSdm_QQIw.jpeg" /><figcaption>Credit <a href="https://unsplash.com/">https://unsplash.com</a></figcaption></figure><h4>Exposure to quality software improves programming skills</h4><p>The more you expose yourself to best practice and high-quality code, the more it will become ingrained and manifested as habit.</p><p>Contributing is a great opportunity to practice coding and get helpful feedback from more experienced developers. By delving into the codebase, you can observe how other people have solved similar problems, and you may discover new patterns for future solutions. It can also provide you a richer understanding of the inner workings of packages and software that you may use every day. You can use these new insights to take full advantage of a tool and maximise its utility.</p><h4>Finding new tools and ways of working</h4><p>With this exposure, you might discover new tools and ways of working. For beginners, contributing can teach you how to use versioning software such as git, as well as how to write a clear commit message. Our team also discovered <a href="https://pre-commit.com/">pre-commit</a>, a tool that checks your code for any mistakes before you commit to your branch. You can set up hooks such as <a href="https://github.com/psf/black">black</a> to format your code, or <a href="https://github.com/Lucas-C/pre-commit-hooks-bandit">bandit</a> to detect any security issues.</p><p>It can also teach you ways of working, such as having a comprehensive CI/CD pipeline to ensure that only quality code gets merged, as well as how to write clear and detailed documentation.</p><h4>Learn how to take feedback</h4><p>Learning how to take feedback and incorporate it is integral to your growth. Don’t be disheartened if you are asked for changes; I made a mistake in <a href="https://github.com/pandas-dev/pandas/pull/32103">my first pull request</a>, but the reviewer was very supportive and spent more time helping me to correct the problem than it would have taken them to fix the issue themselves.</p><h4>Progress your career</h4><p>Contributing is a great way to demonstrate your experience and passion outside of work. You can up-skill in different areas that interest you, and that you may not get the chance to demonstrate in your day-to-day job. At Sainsbury’s we have an engineering career framework, where contributions outside of work projects can be considered as a competency. Whether you’re looking for your next opportunity, or looking for a promotion, contributing can be a useful platform to move your career in the right direction.</p><h4>Gain confidence contributing to team projects</h4><p>It is not only technical skills that you will gain from contributing, but it will also build your confidence. Imposter syndrome is a stumbling block that will affect most people at some point in their careers, so this may help you to start believing in your abilities and speak up in your team’s projects.</p><h4>Grow your network</h4><p>When you are collaborating with other people on these projects, it’s also a great chance to speak to other developers and make connections. You can link your GitHub to LinkedIn so that other people can connect with you (or even recruit you).</p><h4>Give back</h4><p>It is not only these skills that you will develop, it’s also lots of fun to work with other people on projects that you are interested in, and it feels really good to give something back to the community. If it weren’t for people like yourself wanting to contribute, we wouldn’t have all of these cool new tools and technologies at our disposal (well not for free anyway).</p><h4>Street cred</h4><p>It’s pretty cool to say that you’ve contributed to an open source project.</p><h3>Why should companies care?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*VxX1xWuh4kr-7LXoCd_swQ.png" /></figure><p>Hopefully you recognise the benefits to your individual development, but why should companies care or even encourage their developers to contribute to open source?</p><p>Firstly, your personal development is in the company’s best interest; better developers mean a better &lt;<em>insert company name here</em>&gt;. You are better equipped to abstract what you learn from these projects, and apply them in your job, suggesting new ways of working in your team. Companies should consider allocating dev time, viewing your development as an <em>investment</em> with tangible returns.</p><p>It also provides a blueprint for your company to ensure that they are consistently following best practices, as well as cultivating an inclusive dev culture where everybody can contribute.</p><p>Finally, it can also shine the spotlight on your company as leaders in technology. Recognition as a tech company is not exclusively reserved by the likes of Google, Amazon, Facebook, and Apple; the brand recognition that your company could gain is invaluable, and in turn will attract the best engineering talent.</p><p>So if your company doesn’t contribute to open source already — point your manager to this article to convince them!</p><h3>How simple is it really? A step-by-step guide</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U6BoPe_yAVhf-LXclAHnJg.png" /></figure><p>Now that you are adequately persuaded, or you’ve skipped to this section because you’re ready to get going, I will now outline the steps that you will need to take to make your first contribution. Contributing to open source generally follows a pattern, however, if you get confused, most projects will have clear and detailed documentation on how to contribute, usually called ‘<a href="https://github.com/pandas-dev/pandas/blob/master/.github/CONTRIBUTING.md">CONTRIBUTING.MD</a>’.</p><h4>Choosing a project</h4><p>Firstly, you’re going to want to choose a project that you would like to contribute to. We chose the python package pandas because we use it regularly and wanted to get a better understanding of the inner workings.</p><h4>Choosing an issue to work on</h4><p>Once you have chosen your project, head to the GitHub issues tab. You can usually filter issues by their tags which makes it simpler to identify what you would like to work on. If it is your first time contributing, there are often tags such as ‘<a href="https://github.com/pandas-dev/pandas/labels/good%20first%20issue">good first issue</a>’. You can usually find tickets for updating readmes or docstrings which is a great place to start. For those more experienced, you can always filter by the type of issue that you would like to tackle such as ‘testing’ or ‘refactor’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*_qYGdjhKDlj1aN0Bj0hs_Q.png" /></figure><p>Once you have identified your issue, comment on the issue to let others know that you are working on it.</p><h4>Step 1 — Fork, clone and set-upstream</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*5qCq-MYnEEzVJFjyjsC12Q.png" /></figure><p>Instead of directly cloning the repo, you will have to fork the repo and clone that. This avoids open source projects from becoming cluttered with multiple branches; when you make your pull request you will simply compare your branch on your fork against the master branch of the original repo.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/fa92be5feeff49bafee695623b1ac180/href">https://medium.com/media/fa92be5feeff49bafee695623b1ac180/href</a></iframe><h4>Step 2 — Set up development environment</h4><p>You will need to follow the instructions in the contribution documentation to ensure that you have the right setup and to install any dependencies. Pandas provides clear instructions on how to do this; you can either install a C compiler and create an isolated pandas development environment, or if like me you want to avoid any manual setup, I used the <a href="https://www.docker.com/">DockerFile</a> provided to launch a <a href="https://code.visualstudio.com/docs/remote/containers">remote session with Visual Studio Code</a> (IDE).</p><h4>Step 3 — Fix the issue</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9f78f6e1e8cc4cf3c0cb28cca30729e8/href">https://medium.com/media/9f78f6e1e8cc4cf3c0cb28cca30729e8/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fw088yn56bAmyKCuWi_-Iw.png" /></figure><p>In this fix, we only introduced 2 new lines of code. We triggered the error in order to ascertain the correct error message for our test and copied that.</p><h4>Step 4 — Prepare for your pull request</h4><p>Before you commit any code, pandas asks you to run a few commands which follow some best practice principles, for example, run <a href="https://github.com/pytest-dev/pytest">pytest</a>, format code using black, and confirm that you are using the latest code in your branch. They helpfully provide reminders in the pull request template if you forget.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ccbaa64f4fb2a6c8d60b71d03f7a7cc4/href">https://medium.com/media/ccbaa64f4fb2a6c8d60b71d03f7a7cc4/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*8-SctQs9qa9BxMcxmK7_Rg.png" /></figure><p>Now you are ready to create your pull request. Fill in the pr template with as much detail as possible.</p><h4>Step 5 — Review</h4><p>When you raise your pull request, your changes will automatically trigger the CI/CD pipeline which will run tests against your code. If these all pass, then it will move onto a human review. If there are any changes that need to be made, a maintainer will give feedback for you to incorporate and try again (go back to step 3 and fix the issue). When your fix is accepted by the reviewer, they will merge your code into master.</p><h4>Congratulations you are now a contributor</h4><p>That’s it. Fork the repo, set up the development environment, fix the issue, create a pull request, and get your code reviewed. It really is that easy.</p><p><a href="https://github.com/pandas-dev/pandas/pull/32103"><em>Link to my first contribution</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e4771c4b427" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sainsburys-engineering/open-source-is-easy-8e4771c4b427">Open source is easy</a> was originally published in <a href="https://medium.com/sainsburys-engineering">Sainsbury’s Tech Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>