<?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 Blair on Medium]]></title>
        <description><![CDATA[Stories by Blair on Medium]]></description>
        <link>https://medium.com/@Blair-Young?source=rss-309f538e0755------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*uMbzdNBd4C63JCGK8PvUCQ.jpeg</url>
            <title>Stories by Blair on Medium</title>
            <link>https://medium.com/@Blair-Young?source=rss-309f538e0755------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 10:52:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Blair-Young/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[Weekly newsletter of Ethical AI — Issue #3]]></title>
            <link>https://medium.com/@Blair-Young/weekly-newsletter-of-ethical-ai-issue-3-f75c77f57c3b?source=rss-309f538e0755------2</link>
            <guid isPermaLink="false">https://medium.com/p/f75c77f57c3b</guid>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[ethics]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Blair]]></dc:creator>
            <pubDate>Mon, 26 Apr 2021 10:37:39 GMT</pubDate>
            <atom:updated>2021-04-26T10:37:39.791Z</atom:updated>
            <content:encoded><![CDATA[<h3>Weekly newsletter of Ethical AI — Issue #3</h3><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*_wpNDRHscQw2c9MQ" /><figcaption>Ethical AI, Inclusivity at the forefront</figcaption></figure><h3>Hey all!</h3><p>Welcome to the third issue of Ethical AI 👋</p><p>We’ve got quite a bit of content this week: Hands-on ethical exercises, warning signs with AI and healthcare, and of course, the biggest news of the week- the landmark AI regulation framework from the European Union.</p><p>Let’s get started!</p><h3>Intro to AI ethics course</h3><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*Wy6ItkXAmF3NRxFG" /><figcaption>Student studying by Green Chameleon on Unsplash</figcaption></figure><p><a href="https://www.kaggle.com/learn/intro-to-ai-ethics">Kaggle</a>, a popular competitive data science platform has published an introductory course exploring the moral design of AI systems. The course gives an overview of human-centered design, bias, fairness, and model cards. Even though the course is quite short (maybe a single afternoon), it contains great hands-on exercises and extra resources that will set you down a rabbit hole for quite some time 🐰</p><h3>Hard choices: AI in health care</h3><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*WEK-0vvqsbmN_X9V" /><figcaption>Doctor with phone by National Cancer Institute on Unsplash</figcaption></figure><p>This <a href="https://medicine.yale.edu/news/yale-medicine-magazine/hard-choices-ai-in-health-care/">article</a> by <a href="https://www.linkedin.com/in/jennifer-huizen-b61703aa/">Jennifer Huizen</a> gives a great insight into how AI in medicine has veered off the benign path of doctor augmentation and towards pressurized environments, where doctors may start to be legally accountable for overriding AI decisions.</p><p><em>“Before, a doctor could see when their scalpel needed to be sharpened,” Wallach said, “Now for all intentional purposes doctors are working off of an invisible scaffold with invisible tools.”</em></p><h3>European regulation of AI</h3><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*GbHcqM8omSb7oieF" /><figcaption>European Union flag by Christian Lue on Unsplash</figcaption></figure><p>It’s a big one! The European Union has commissioned the first legal framework to address the impact of AI on the rights of people and businesses. The <a href="https://digital-strategy.ec.europa.eu/en/library/proposal-regulation-european-approach-artificial-intelligence">108-page document</a> draws out a risk-based approach to AI and trust. The framework not only classifies AI use cases but sets out obligations each AI system must abide by before going to market. Check out this summary <a href="https://ec.europa.eu/commission/presscorner/detail/en/ip_21_1682">here</a>.</p><p>This is a true milestone to ground the very much wild-west technology of AI. I’m sure many companies will be concerned that these regulations may stifle innovation, but it’s time we pumped the breaks and take a look at the impact we’ve made already. We will be breaking down this framework in subsequent issues so keep an eye out for that! 👀</p><p>That’s a wrap 🎁 Thanks for reading if you have anything that you feel would be suitable for the newsletter or just want a chat please get in contact either at <a href="/service/mailto:ethical.ai.newsletter@gmail.com?utm_campaign=Weekly%20newsletter%20of%20Ethical%20AI&amp;utm_medium=email&amp;utm_source=Revue%20newsletter">ethical.ai.newsletter@gmail.com</a> or reach out on <a href="https://www.linkedin.com/in/blair-young-data/?originalSubdomain=uk&amp;utm_campaign=Weekly%20newsletter%20of%20Ethical%20AI&amp;utm_medium=email&amp;utm_source=Revue%20newsletter">LinkedIn</a>.</p><p>See you all next time 👋</p><p>Blair</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f75c77f57c3b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weekly newsletter of Ethical AI — Issue #2]]></title>
            <link>https://medium.com/@Blair-Young/weekly-newsletter-of-ethical-ai-issue-2-7b5be4cd7a27?source=rss-309f538e0755------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b5be4cd7a27</guid>
            <dc:creator><![CDATA[Blair]]></dc:creator>
            <pubDate>Mon, 12 Apr 2021 06:28:36 GMT</pubDate>
            <atom:updated>2021-04-12T06:28:36.056Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*xSzFLb4cEUan0I3G" /><figcaption>Ethical AI, Inclusivity at the forefront</figcaption></figure><p>It’s issue two… Multiple issues! I suppose we can start calling this a series now 💪</p><p>That’s enough of a pat on the back. Let’s dive into stories 🐬</p><p>In this issue we’ve got steps in the right ethical direction at Facebook 🐾, AI governance 🔦 and a paper highlighting surprising model behaviour when unexpected loopholes are exploited during training ➰</p><h3>Fairness Flow @ Facebook</h3><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*JSWA9Uapo4YuTl-U" /><figcaption>Group analysis from Fairness Flow</figcaption></figure><p>Facebook has developed <a href="https://ai.facebook.com/blog/how-were-using-fairness-flow-to-help-build-ai-that-works-better-for-everyone/">Fairness Flow</a>- An internal toolkit for assessing statistical bias within datasets. The quality of a model’s predictions is reflective of the material it learns from- “Garbage in, garbage out”. This can also be said for bias: feed a model biased data, you should expect biased outcomes.</p><p>Fairness Flow identifies bias across two areas, model and label fairness. Model fairness ensures outcomes are equally performant across different groups of people and label fairness ensures a more formal framework for proper labelling of data.</p><p>This is a great step in the direction of inclusive technology, but it’s still lacking transparency. Although Facebook have consulted with experts (Stanford, <a href="https://csmr.umich.edu/">Center for Social Media Responsibility</a> and <a href="https://www.bbbmarketplacetrust.org/">Better Business Bureau Institute for Marketplace Trust</a>) it’s still an internal tool, it’s success and resultant performance is still in the eyes of the beholder, will this toolkit ever be released for a public audit?</p><h3>Social Media Ethics Ratings with EthicsGrade</h3><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*hITChsKgv8v6ydZt" /><figcaption>Social media apps by dole777 on Unsplash</figcaption></figure><p><a href="https://ethicsgrade.io/">EthicsGrade</a>, an governance rating agency has published ratings for <a href="https://techcrunch.com/2021/03/31/startup-rates-the-algorithmic-ethics-of-social-media-platforms-targets-asset-managers/?guccounter=1&amp;guce_referrer=aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS8&amp;guce_referrer_sig=AQAAAEppYGVvw1JmAsrMOf1yphXMo3q0CjpZLDGYhPhlMPcrvejo7Ps2ASnLJy1DqOY9ejo7R6Rs7ZoyrDg7nz_gFWYABppxQw6u0Cohec0xTg7kOCPolbC7HyuMpZtTgqlv1Jtq1cJqhgmnOtB7QudImE8Ub0_oKb42cmQHOSqR3Akq">social media platforms.</a></p><p>Similar to companies being held accountable for their carbon footprint or animal welfare, EthicsGrade scores companies based on their AI governance. They do this by collecting and analysing publicly available data, internal assessments, and surveys from each company.</p><p>Their goal is not only to highlight areas for companies to improve, but also to bring to attention the potential risks for asset managers and owners when investing in new ventures.</p><p>You can check out their rating database <a href="https://ethicsgrade.io/ratings/">here</a> and you can also read their process for evaluating companies in their <a href="https://osf.io/preprints/socarxiv/gj2kf/">whitepaper</a>.</p><h3>Alignment of Language Agents</h3><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*0T1z2nmHjAnQt11N" /><figcaption>Ploughed field by Dan Meyers on Unsplash</figcaption></figure><p>In order for models to behave in accordance with what humans desire, we must ensure alignment between what a systems designer intends and what they actually implement.</p><p>This <a href="https://arxiv.org/pdf/2103.14659.pdf">paper</a> from DeepMind highlights the factors we should be thinking about in order to reduce the likelihood of misspecification and examples of resultant undesired model behaviour.</p><p>This paper is very broad (even the first statement of what humans desire is a whole field onto itself) but the authors do a great job in raising awareness in regards to the surprisingly sinister behaviour from AI.</p><p>Second newsletter done and dusted ✅. Thanks for reading, if you have anything that you feel would be suitable for the newsletter or just want a chat please get in contact either at <a href="/service/mailto:ethical.ai.newsletter@gmail.com?utm_campaign=Weekly%20newsletter%20of%20Ethical%20AI&amp;utm_medium=email&amp;utm_source=Revue%20newsletter">ethical.ai.newsletter@gmail.com</a> or reach out on <a href="https://www.linkedin.com/in/blair-young-data/?originalSubdomain=uk&amp;utm_campaign=Weekly%20newsletter%20of%20Ethical%20AI&amp;utm_medium=email&amp;utm_source=Revue%20newsletter">LinkedIn</a>.</p><p>See you all next time 👋</p><p>Blair</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b5be4cd7a27" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ethics and AI — Issue #1]]></title>
            <link>https://medium.com/@Blair-Young/ethics-and-ai-issue-1-a0dd541440d4?source=rss-309f538e0755------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0dd541440d4</guid>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[ethics-in-tech]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Blair]]></dc:creator>
            <pubDate>Sat, 27 Mar 2021 22:26:01 GMT</pubDate>
            <atom:updated>2021-03-27T22:26:01.045Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*elMcai1DM3xs3A4K" /><figcaption>Ethical AI, Inclusivity at the forefront</figcaption></figure><p>Hey everyone and welcome to EthicalAI, a newsletter highlighting the need for inclusivity to be at the forefront of algorithmic design 👋</p><p>I’m sorry… what?</p><p>In a nutshell, an algorithm is a set of instructions to perform a task, basically a recipe from a cookbook. Follow the instructions and get a tasty output. We have algorithms for <em>everything</em> — as simple as <a href="https://www.youtube.com/watch?v=xli_FI7CuzA">sorting</a> values to <a href="https://www.youtube.com/watch?v=6altVgTOf9s">speech recognition</a>. Now here’s the problem- we have algorithms for <em>everything.</em> Every aspect of our lives is being dictated by algorithms, for better or for worse.</p><p>This is why inclusivity is needed. Currently, algorithm’s are created in a sterile environment by a narrow set of people. I’m sure a lot of these people are well-intentioned when creating their idea of a perfect algorithm, however, that’s the problem- Their idea of a perfect algorithm can in fact be exclusionary and lead to discrimination in the wider population.</p><p>In this newsletter, we’ll be bringing you content from around the world spotlighting issues or achievements in the world of AI ethics 🗺</p><p>The inspiration for this newsletter came from starting a job teaching in the tech industry. I’m a Lead Teacher &amp; Data Scientist at <a href="https://www.lewagon.com/">Le Wagon</a> London. Our aim is to improve data literacy on a global scale. As we are educating the next wave of data-driven people, we have a massive responsibility to ensure everyone is aware of ethics within technology, and are actively designing algorithms with inclusion at the forefront 👀</p><p>Let’s jump into it!</p><h3>Coded Bias</h3><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*pP1zt_grNJYnks1T" /><figcaption>Joy Buolamwini</figcaption></figure><p><a href="https://www.codedbias.com/">Coded Bias</a>- The multi-award-winning documentary directed by <a href="https://www.linkedin.com/in/shalini-kantayya-3407363/">Shalini Kantayya</a> explores the social implications of artificial intelligence by following MIT Media Lab researcher <a href="https://www.linkedin.com/in/buolamwini/">Joy Buolamwini’s</a> journey into pioneering the first government legislation to regulate algorithmic bias in the United States 🏛</p><p>At Le Wagon we were lucky enough to host a screening of the documentary followed by a <a href="https://www.youtube.com/watch?v=t-a1rU9_mzw&amp;t=3s">Q&amp;A </a>with Shalini. Check out the trailer <a href="https://youtu.be/jZl55PsfZJQ">here</a> and for anyone living in the UK, it will be available on Netflix 5th of April.</p><h3>Beyond the promise: implementing ethical AI</h3><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*eMQsfZf06LbN9-pY" /><figcaption>Windy road by Markus Gempeler on Unsplash</figcaption></figure><p><a href="https://link.springer.com/article/10.1007/s43681-020-00011-6">Beyond the promise: implementing ethical AI</a>- By 2022 it’s expected that 85% of AI projects are expected to deliver erroneous outcomes due to bias. This paper identifies the common pitfalls associated with corporate AI and illustrates ethical governance steps businesses must take to mitigate risks associated with AI development 🛣</p><h3>Weapons of Math Destruction</h3><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*VmYn6WZsQNBLO7Bt" /><figcaption>A battered copy of Weapons of Math Destruction</figcaption></figure><p><a href="https://www.goodreads.com/book/show/28186015-weapons-of-math-destruction">Weapons of Math Destruction</a>- Mathematician, <a href="https://twitter.com/mathbabedotorg">Cathy O’Neil</a> sheds light on the need for algorithmic accountability using examples from education, advertising and insurance policies. This book is by no means new, but I do think this is a great first step for anyone to get into the world of algorithmic ethics. 🧮</p><p>Phew! 😅</p><p>That’s it, the first newsletter complete ✅ Thanks for sticking around. If you have anything that you feel would be suitable for the newsletter or just want a chat please get in contact either at <a href="/service/mailto:ethical.ai.newsletter@gmail.com">ethical.ai.newsletter@gmail.com</a> or reach out on <a href="https://www.linkedin.com/in/blair-young-data/?originalSubdomain=uk">LinkedIn</a></p><p>See you all next week 👋</p><p>Blair</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0dd541440d4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Get Stuck in with Contributing to pandas]]></title>
            <link>https://medium.com/data-science/get-stuck-in-with-contributing-to-pandas-fea87d2ac99?source=rss-309f538e0755------2</link>
            <guid isPermaLink="false">https://medium.com/p/fea87d2ac99</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[pandas]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[data-science]]></category>
            <dc:creator><![CDATA[Blair]]></dc:creator>
            <pubDate>Thu, 10 May 2018 13:20:45 GMT</pubDate>
            <atom:updated>2021-05-14T22:38:03.288Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NSNdiqWeKjCf79G8" /><figcaption>Photo by <a href="https://unsplash.com/@bolotohodova?utm_source=medium&amp;utm_medium=referral">Polina Razorilova</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Hands up if this strikes a chord with any data people out there. Your boss gives you a dataset and asks you to find something interesting. You grab the data and stick it into a Jupyter Notebook. Now what? Chances are your fingers have already subconsciously typed out:</p><pre>import pandas as pd</pre><p>In this post, we’re not going to navigate through the nitty-gritty of what <a href="https://pandas.pydata.org/">pandas</a> is or how to use it, chances are you probably know your way around the library better than I do! Instead, I’ll focus on giving back to the data analysis community through documentation.</p><p>I came across a pandas sprint session while attending PyData London 2018. It was here I learned that the popularity of the open source package has outpaced the level of contribution, in particular its API documentation.</p><p>Similar to the <em>wisdom of the crowd </em>phenomenon, which suggests it’s better to take an opinion from a group, rather than taking an individual’s word as gospel — open source allows experts and amateurs alike to collaborate on a project that can benefit a community as a whole.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*D36URMxtTud_yhRwG4QoAQ.gif" /></figure><p>Until this sprint, I hadn’t really contributed towards open source — honestly, I never really believed my coding chops were up to scratch. However, I am a stickler for well documented code, so the fact this sprint focused on documentation gave me some much needed confidence.</p><p>So if my story resonates with you and you’ve never contributed to an open source project but want to do so, keep reading and I’ll guide you through the process.</p><h3>Lets contribute to pandas</h3><h4>Setting up</h4><p>I could go through the setup steps here, but there is no point reinventing the wheel…check out the super succinct pandas sprint setup instructions <a href="https://python-sprints.github.io/pandas/guide/pandas_setup.html">here</a>.</p><p>Now that everything is in order🤞 , let me explain what good documentation looks like and why we need it.</p><h4>Documentation 101</h4><p>Documentation is a set of concise information regarding the use of a particular function, method, class or module. Without it, the user will either misinterpret the tools purpose, or waste time trying to understanding source code. Basically, documentation aims to reduce the time needed to understand how to use a tool so the user can get on with their job.</p><p>So what information do I include?</p><p>I’m glad you asked, here’s a list of 7 sections to include in a your documentation…you won’t believe number 5!</p><p><strong>Section 1- Short summary</strong></p><p>This is the first thing a user sees so make it punchy! A short, sharp sentence describing the essence of the function.</p><p><strong>Section 2- Extended summary</strong></p><p>Not everything can be described in a single sentence and that’s OK. This section allows you to describe the nuances of the function in a bit more depth.</p><p><strong>Section 3- Parameters</strong></p><p>Here you provide the user with a set of inputs required by the function. These must include a type and a description for each parameter.</p><p><strong>Section 4- Returns</strong></p><p>If the function returns a value or alters a state, it’s imperative this is brought to the users attention as misunderstandings can have severe consequences downstream. Make sure you document it here.</p><p><strong>Section 5- See also</strong></p><p>In this section the documentation tries to bring the users attention to other related functions. Relating to other functions may give the user a more intuitive understanding.</p><p><strong>Section 6- Notes</strong></p><p>This is an optional section, any details that weren’t explained in the ‘Extended summary’ can be discussed here.</p><p><strong>Section 7- Examples</strong></p><p>People like to learn by doing, there’s no better way to concrete the understanding of a concept than by using it in a real scenario. You should include a few examples on how the function could be used.</p><h4><strong>Documentation walk-through</strong></h4><p>On the day of the sprint each participant was given a function or method to document — I was designated <a href="https://pandas.pydata.org/pandas-docs/stable/generated/pandas.Series.str.contains.html">pandas.Series.str.contains</a>. So just like <strong>Section 7, </strong>I’ll talk you through this example.</p><p><strong>Step 1- Initial overview</strong></p><p>Check out the current state of the documentation. Create a checklist of the potential areas of improvement and get that much needed dopamine fix after ticking each one off.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FRZgyjl_anpCDmTGcxkIuA.png" /></figure><p>As you can see, some sections discussed above are absent, there are a couple of discrepancies in regards to parameter types and a few formatting issues. Overall, not too shabby.</p><p><strong>Step 2- Give the function a test drive</strong></p><p>Before you can write about a function, you’ve got to understand the function, this is essential. Think of as many conceivable reasons why you would want to use this in day to day programming, then implement some basic use cases. These can then be used in <strong>Section 7 </strong>as examples. You could also further clarify your understanding of the function by writing a couple of unit tests.</p><p><strong>Step 3- Who else is in the same boat?</strong></p><p>Remember, the reason why we’re doing this is to help people understand code efficiently. Search the function on Google, Stack Overflow or Github and see if anyone has had problems previously. If similar questions keep popping up, tailor the documentation towards them to clear up any ambiguity. When searching for problems with pandas.Series.str.contains I kept coming across <a href="https://stackoverflow.com/questions/19169649/using-str-contains-in-pandas-with-dataframes">questions</a> involving regular expression. To deal with this, I made sure to include a few of these in the related examples.</p><p><strong>Step 4- Conformity</strong></p><p>Different minds have different styles and generally speaking variety is a good thing. However, as a code base grows, consistency is crucial. With python, most libraries try to follow code formatting guidelines, pandas follows <a href="https://www.python.org/dev/peps/pep-0257/">PEP 257</a>. This includes guidelines on everything from whitespaces to the use of infinitive verbs. This might sound pedantic, but these guidelines have been modified and tweaked for almost two decades, they are there for a reason — so use them!</p><p>Luckily, the core developers of pandas have built a script that checks if your code is compliant with their style guidelines. It’s handy to run this every so often and correct your code accordingly.</p><pre>python scripts/validate_docstrings.py &lt;insert-your-function-here&gt;</pre><p>You should also run the well known python linter, flake8 to keep everything tidy.</p><pre>git diff upstream/master -u -- &quot;*.py&quot; | flake8 --diff</pre><p>Once you feel like the documentation is up to standard, give it a quick preview with:</p><pre>python make.py html — single pandas.Series.str.contains</pre><p>Looks good? Time for a pull request. Check out this <a href="https://python-sprints.github.io/pandas/guide/pandas_pr.html">page</a> for pushing your suggestions.</p><p>This stage involves you publishing your suggestions to the core developers, if they like your suggestions, they’ll accept it for the next release.</p><p>Just one more thing…the core developers will know more about good documentation than you, so they may have some suggestions about your suggestions. My advice is don’t take it to heart, just rinse and repeat, do the fixes and push to your pull request.</p><p>Don’t be afraid of making your mistakes public, feedback is your friend. Otherwise you’ll never learn from your mistakes, or worse — compound a bad habit. Remember the core developers are crying out for people like you who want to help!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*vTaMIThH5hHUNhixtcxqWQ.gif" /></figure><p>So here it is, in all its glory, checkout my improved version of <a href="https://pandas.pydata.org/pandas-docs/stable/generated/pandas.Series.str.contains.html">pandas.Series.str.contains</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PPohenFaX91cCzvlGdSIxw.png" /></figure><p>You can see I’ve given a clear and concise description of the method, added and an extended summary, spruced up the parameters, tidied the returns section and added a tonne of typical use cases.</p><p>If this beautiful piece of documentation has inspired you to try your hand at contributing to pandas (or any other project), sift through the documentation <a href="https://pandas.pydata.org/pandas-docs/stable/">here</a> and try and scope out anything you think you can improve upon. If you are unsure what to delve into, you can return a list of documentation that needs improving by using this script:</p><pre>python scripts/validate_docstrings.py</pre><p>So there we go! I hope that gave you a bit of confidence to start your journey of becoming an open source contributor. Thanks for reading, and if you have any questions leave them in the comments section below.</p><p>I would also like to thank <a href="https://twitter.com/datapythonista?lang=en">Marc Garcia</a> for guiding the pandas documentation sprint.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fea87d2ac99" width="1" height="1" alt=""><hr><p><a href="https://medium.com/data-science/get-stuck-in-with-contributing-to-pandas-fea87d2ac99">Get Stuck in with Contributing to pandas</a> was originally published in <a href="https://medium.com/data-science">TDS Archive</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>