<?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 michelle hoffman on Medium]]></title>
        <description><![CDATA[Stories by michelle hoffman on Medium]]></description>
        <link>https://medium.com/@hoffman.michelle.e?source=rss-f4b2c5704d5e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*bDDJcEME0I16k95J.</url>
            <title>Stories by michelle hoffman on Medium</title>
            <link>https://medium.com/@hoffman.michelle.e?source=rss-f4b2c5704d5e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:08:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hoffman.michelle.e/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[A First Timer’s Contribution to Open Source]]></title>
            <link>https://medium.com/@hoffman.michelle.e/a-first-timers-contribution-to-open-source-d0c9b0af059a?source=rss-f4b2c5704d5e------2</link>
            <guid isPermaLink="false">https://medium.com/p/d0c9b0af059a</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[michelle hoffman]]></dc:creator>
            <pubDate>Fri, 30 Mar 2018 03:08:16 GMT</pubDate>
            <atom:updated>2018-03-30T03:12:34.860Z</atom:updated>
            <content:encoded><![CDATA[<p>I am a Front End Engineering student at the Turing School of Software &amp; Design; a soon-to-be graduate, actually. Just a few months ago, I had almost zero experience in programming. The terminal was a dark, scary place and forget about dealing with vim.</p><p>Now, I’m amazed at just how much I’ve grown since starting this program. Sure, I’ve learned about syntax, writing DRY code, functional and object oriented programming, etc. But the most valuable thing I’ve learned is how to tackle the unknown. To take a large problem and break it down into small bite-sized pieces.</p><p>Making a contribution to open source always sounded like a daunting task. Something for experts to dabble in. My classmates and I have only written in our own separate codebases up until now. We’ve had plenty of paired projects, but also had a hand in writing that code from the very beginning. Stepping into a foreign codebase, especially a large one, is a really intimidating thing.</p><p>For one our our final projects at Turing, my team was assigned to contribute to Iodide’s open source project. This project is a notebook-style application where scientists will be able to display their findings visually and allow other users to view their code and interact with it. Iodide-Project is built with technologies such as React, Redux, Material UI, Enzyme, and Jest to name a few.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SjuzX1UvMQucscU-2p_Bug.png" /></figure><p>The first thing we did in beginning this process was to read over the README.md and contributing guidelines and play around with the application in the browser. Once we felt that we had a good understanding of how the application worked, we looked through the issues labeled “good first issue.” Ultimately, we chose one that sounded very simple as an introduction to the code, a simple margin fix.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m4mek_9Z0bnepFAUik2b4A.png" /><figcaption>The first issue my team tackled in our open source contributions.</figcaption></figure><p>This issue sounded maybe even too easy, but we we had never worked with Material UI before. We located the element with Chrome’s dev tools and spent a while looking for the saved text element with a class of <em>MuiTypography-root-38</em>. After trying to find an element with that class and having no luck, we settled for looking into it’s parent element, a div with the class <em>view-controls</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/662/1*g1ShzwPROl82v0hv5PBbcg.png" /><figcaption>Highlighting the parent div with dev tools.</figcaption></figure><p>Relatively quickly, we were able to track down a component called ViewControls in the components directory. Inside of that component’s render we found our LastSavedText component. We finally stumbled upon the correct component, but then we were a little confused when we noticed the Typography element in the render method of LastSavedText. Once we realized that Typography was being imported from Material UI, we had to figure out how to style it.</p><p>We didn’t want to style every Typography element, so targeting Typography in the stylesheet was out of the question. I was unsure if it was acceptable to add a class attribute to an existing element, so we dug into some of the other components to see if inline styling had been used. And it was!</p><p>We decided to add a right margin of 10px to this instance of the Typography element via a style attribute. In React that looks a little something like this:</p><blockquote>&lt;Typography style={{ marginRight: 10px }}&gt;&lt;/Typography&gt;</blockquote><p>It seems like a simple fix, but I think this was a great introductory issue. We created a Pull Request to merge our changes into the master branch and it was accepted!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3zHIrc_RwWyxTFs3ttr_nA.png" /></figure><p>We went on to tackle another issue; this time one that was labeled as a bug. This second issue was also solved relatively easily and ended up being merged. These were both small contributions, but I’m really proud that my teammates and I were able to work through a strange codebase with a clear head and approach problems logically.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d0c9b0af059a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>