<?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 Chelsea Carr on Medium]]></title>
        <description><![CDATA[Stories by Chelsea Carr on Medium]]></description>
        <link>https://medium.com/@ChelseaCarr?source=rss-48df02b2144c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_KApoyUTFcKAs1nbwz5Aig.jpeg</url>
            <title>Stories by Chelsea Carr on Medium</title>
            <link>https://medium.com/@ChelseaCarr?source=rss-48df02b2144c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 23:24:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ChelseaCarr/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[Software Engineering: A Learning Addict’s Paradise]]></title>
            <link>https://medium.com/yello-offline/software-engineering-a-learning-addicts-paradise-7170fce9924e?source=rss-48df02b2144c------2</link>
            <guid isPermaLink="false">https://medium.com/p/7170fce9924e</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Chelsea Carr]]></dc:creator>
            <pubDate>Mon, 11 Sep 2017 16:16:02 GMT</pubDate>
            <atom:updated>2017-09-11T16:16:02.136Z</atom:updated>
            <content:encoded><![CDATA[<p>I didn’t begin my developer journey until my first year of college. I tried to take a programming course in high school, but my school didn’t seem too keen on that &lt;Insert angry rant about women in technology here&gt;. I did take a lot of math and science courses, as well as a few hands-on skilled trade courses, such as woodworking and welding. I like solving logic puzzles, playing video and board games, and generally anything requiring strategy or critical thinking. Naturally, I was very interested in a career in software development.</p><p>When I took my first college-level computing course, I had already made up my mind that I was going to accomplish two things during my undergraduate: 1) Earn my degree in Computer Science and 2) Learn everything there is about software. Earning my degree was a pretty straight forward goal, but I clearly didn’t understand that completing 2 was next to impossible and I could spend my whole career trying to accomplish that.</p><p>A funny thing happens when you decide to go into a STEM-based career. You might think, “I will get a degree in &lt;insert engineering specialty here&gt;, and then I will be done learning.” You’d be correct for all of 90 seconds. In the tech industry, the real world looks an awful lot like those late nights I pulled during college, picking up new languages and refining the skills I’d recently acquired.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wuaryaQQv35QQ0nmS7xs9w.jpeg" /><figcaption>Surprise! My learning fuel of choice is coffee. This photo is licensed under the <a href="https://burst.shopify.com/licenses/creative-commons">Creative Commons License </a>on <a href="https://burst.shopify.com/photos/tablet-coffee">Burst</a></figcaption></figure><h3>Learn All the Things</h3><p>I started by learning Basic, then moved on to Python, C, C++, and SPARC Assembly. I taught myself HTML, CSS, PHP, Javascript, and SQL so I could find a part time job. From there, it spiraled out of control. Every semester I was coding in one to two “familiar” languages and working in three to four that were new to me. By the end of my third year of college, I had worked in about 16 languages. This helped me find new coding opportunities, but it also made it very difficult to keep all the syntax straight during interviews. By my last year in college, I had experimented with enough languages that I would have quite a few choices for my senior project.</p><p>Looking back now, <strong>If I hadn’t taken the time to keep seeking out new languages to learn, I would have likely been siloed into a single path for my senior project and probably my career. </strong>I feel like many people assume that if you have a Computer Science degree, picking up a new language is trivial. Sure, we’re taught a bunch of theory and learn how languages actually work under the hood, but I think practice is ultimately what makes picking up a new language easier each time. You develop the skills and habits that enable the learning process itself, rather than always knowing what to learn.</p><h3>Swiftly Falling Into the Deep End</h3><p>A few years into my career as an iOS developer, the first version of Swift was released. I’d been working almost exclusively in Objective C for that entire time, not really touching any other languages. My knee-jerk reaction when Swift came out was to run. Run far, far, away and stick to the world of overabundant brackets and hybrid C code.</p><p>I was very skeptical of Swift when it first came out. I couldn’t see how to implement everything I wanted to, and I certainly couldn’t work as fast as I was in Objective C. In reality, I was mostly just afraid to leave the familiarity of Objective C behind and move on to something new and different. What if I couldn’t learn it? What if I was not as successful with Swift as with Objective C? Could that cost me my job? Let’s take a moment to talk about these questions.</p><p><strong>What if I couldn’t learn it?</strong> This is ridiculous — I’d been training myself for more than half a decade to be able to learn new things rapidly and successfully. Most of the benefits of my education were not necessarily based on <strong><em>what</em></strong> I was learning, but <strong><em>how</em></strong> I was learning it. I should be able to make a sincere attempt to learn Swift.</p><p><strong>What if I was not as successful with Swift as with Objective C? Could that cost me my job?</strong> The short answer: Absolutely. Part of my job is writing code that isn’t riddled with logic errors, is easily maintained, and not full of misused concepts. If I am incapable of doing any of that, then I should not be working at this job. Picking up new skills and staying up to date on the latest technologies is how I do my job efficiently. <strong>If</strong> <strong>I stop being able to learn, I will not be able to do my job for much longer.</strong></p><p>I knew my employer at the time was not going to start adopting Swift anytime soon, but I was still tempted to give it a chance. I worked through a tutorial and you know what? I was really, really horrible at Swift. I wrote compilable code, but future me would not have been able to decipher the trainwreck of a project I had created.</p><p>It really wasn’t until my current job, nearly two years later, that I am proficient in Swift. I spent all that time reading blog posts, trying new techniques, getting my code peer reviewed, and at some point, something finally clicked. I can work even more efficiently now with Swift than I did in Objective C. I’ve barely scratched the surface at this point, and I still have so much more I could learn about Swift, especially as it continues to evolve and grow under Apple’s stewardship.</p><h3>What’s the Point?</h3><p>I’m just over 4 years into my full-time career and every single day, I learn something new. Sometimes from blog posts and StackOverflow, sometimes from my peers, and sometimes just from my own mistakes. This applies to my non-technical learnings, as well. For example, my first job out of college was creating white-labeled mobile banking apps, which meant I needed to learn and follow the security and federal requirements of the banking industry. If I could go back and tell my past self one thing, it would be that all those long days and late nights studying new technology, really understanding how to learn about those technologies, actually paid off.</p><p>One of Yello’s core values is to <strong>Learn and Be Curious. </strong>I would argue that a Software Engineer’s strongest skill is their ability to learn. Without that skill, there eventually won’t be any forward progress or innovation. Now, I live for the thrill of new technology and exploring the unknown. I’m a Software Engineer by title and a Learning Addict by trade.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7170fce9924e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/yello-offline/software-engineering-a-learning-addicts-paradise-7170fce9924e">Software Engineering: A Learning Addict’s Paradise</a> was originally published in <a href="https://medium.com/yello-offline">Yello Offline</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>