<?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 lauren lee on Medium]]></title>
        <description><![CDATA[Stories by lauren lee on Medium]]></description>
        <link>https://medium.com/@LoLoCoding?source=rss-b6d79fdd930a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*DXRvuE4NXP7TioRLcHvQ0Q.png</url>
            <title>Stories by lauren lee on Medium</title>
            <link>https://medium.com/@LoLoCoding?source=rss-b6d79fdd930a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 19:39:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@LoLoCoding/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[I swear this will be the last time I talk sh*t about myself]]></title>
            <link>https://medium.com/swlh/i-swear-this-will-be-the-last-time-i-talk-sh-t-about-myself-9e7f53cdea20?source=rss-b6d79fdd930a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e7f53cdea20</guid>
            <category><![CDATA[girls]]></category>
            <category><![CDATA[courage]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[imposter-syndrome]]></category>
            <dc:creator><![CDATA[lauren lee]]></dc:creator>
            <pubDate>Mon, 11 Mar 2019 23:31:01 GMT</pubDate>
            <atom:updated>2019-03-12T17:45:58.785Z</atom:updated>
            <content:encoded><![CDATA[<h3>Disclaimer, I originally wrote this in May of 2018.</h3><p><em>I was just about to graduate from </em><a href="http://adadevelopersacademy.org"><em>Ada Developers Academy</em></a><em> and needed to get my nervous feelings out of my head and onto paper. But I didn’t publish it. I couldn’t bring myself to actually press the </em><em>publish button. I was mortified of admitting how insecure I f̶e̶l̶t̶ feel in the tech industry.</em></p><p><em>However, now, almost a year later, with a little bit more experience, a new company, and a new role under my belt, I’ve come to realize that I never was alone in feeling this way. </em><strong><em>So many </em></strong><em>of us face self-doubt, insecurity, and imposter syndrome. So many have also entered the industry via unconventional paths (i.e. bootcamps or self-taught) instead of studying Computer Science in college. And so many similarly question whether or not there is space in this industry for someone like ourselves.</em></p><p><em>While it felt good and cathartic at the time to write this, just for myself, it feels important now to share. Perhaps it’ll resonate with you, who knows 🤷🏼‍♀️ it might not, but I don’t need it taking up space in my drafts folder any longer.</em></p><blockquote>May 2018:</blockquote><p>So here’s the thing. I’m fully aware that nobody wins when I talk sh*t about myself. And yet I cannot seem to stop. Perhaps it’s a bad case of imposter syndrome or an ingrained behavior taught to me by our patriarchal society, but for whatever reason, I lead far too many professional interactions with self-deprecation.</p><p>It’s easy to do in this new field of mine. <em>Or rather, I’ve come up with plenty of excuses for why I do this</em>: You see, I’m a coder but I come from a non-traditional path. I attended a coding bootcamp after being an English teacher for the past 7 years of my life. This means that I don’t have a Computer Science degree like everyone else on my developer team. And while my peers have been in the industry for at least half a decade, I’ve only been coding for about a year!</p><p>And so I often am faced with feelings of not belonging and insecurity. To cope, I degrade my abilities or crack a joke about my ineptitude and hide behind that sarcasm and humor. I do it with a smile and laugh it off- inviting others to join in on the hilarity that is my inadequacy.</p><p>But let’s be real, it’s not funny and it’s not true and is totally 100% a defense mechanism. I do it out of fear that someone will think that I truly don’t belong here. Out of fear that they’ll eventually reveal my hidden truth, see through my facade, and realize that I don’t innately know how to traverse a binary search tree! They’ll discover that I don’t belong. Thus I find myself trying to beat them to the punch by self-sabotaging before someone else can reject me on their own.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/244/1*k5fAL0kixrSWPrU8ceJWUQ.gif" /></figure><p>The thing is that self-deprecating humor can be a good quality. It can demonstrate that someone is self-aware, humble, empathetic, and doesn’t have an ego.</p><p>But more often than not, for me, it becomes a self-fulfilling prophecy. Because, shocker, if you say it enough times, you’ll eventually believe it!</p><p>Recently, I taught a technical IoT workshop on how to build an Alexa-enabled prototype back at Ada. I prepared intensely for it and dedicated hours upon hours to practicing my slide deck and tinkering with my examples to make it perfect. I was well prepared and had developed expert knowledge of the technical content I was delivering. But what do you know? Peppered throughout my presentation were self-deprecating wise-cracks about how little I know about the inner workings of the hardware!</p><p>The worst part? I wasn’t even aware that I was making these jokes. 😳 My mentor had to point it out to me afterward! <em>That’s how ingrained this behavior is.</em> Sometimes I am completely oblivious to the fact that I’m doing it!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JWwYSyvosyjbqJN5ePG12A.png" /><figcaption>Me teaching a technical workshop &amp; demo-ing my expert ability to self-deprecate at the very same time!</figcaption></figure><p>It’s ridiculous. And I know that I’ve got to shake this insecurity. Especially as I begin to interview with new tech companies — this habit of apologizing for myself upon the first impression is seriously going to eff up my chances of ever getting an offer. Further, a serious goal of mine is to continue giving workshops and get more involved in public speaking. I’ve submitted a few proposals to a couple of local conferences. <em>But let’s be real, why would anyone want to want to hear me speak if even I don’t believe I deserve to be there?</em></p><p>I write this, knowing all too well how vulnerable it makes me. It’s probably pretty risky of me to expose such deep insecurity: <strong>the feeling that I don’t belong in this industry. </strong>That perhaps, I may not have the chops to succeed as a coder after all.</p><p>But to hell with it. Because I refuse to believe that I’m the first person to ever feel this way! And perhaps the more we talk about it, the less likely others will be to fall victim to these plaguing feelings of self-doubt in the future.</p><p>And so here I am, standing in my truth, ready to finally stop apologizing for who I am. Yes, you’ve heard it here first folks, today is really the day I actually stop (or at least <em>really really</em> try — remember folks, ingrained behavior can be tough to kick!). After all, who gains from these insecure feelings and this self-deprecating behavior? <strong>Only those who created this male-dominated industry in the first place, that’s who!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*pYu0EXY5eFbUdLEveGd6ZQ.gif" /><figcaption>my favorite line from my favorite movie, The Greatest Showman</figcaption></figure><p>It’s important to note that, by no means, am I filled with self-hate. That’s <em>absolutely</em> not the case. I am so incredibly proud of the choice I made to change career paths after all of those years and pursue my dreams. I love being a developer. And I’m pretty damn good at it!</p><blockquote>In fact, I’m writing this in an effort to remind myself that the things I’m most insecure about may, in fact, be assets that I bring with me wherever I go. Perhaps the skills I learned while being a teacher, a department chair, a volleyball and cross-country coach, and a mentor for all of those years may in fact be skills that my future tech team will benefit from.</blockquote><blockquote>Perhaps my perspective will be different than those who have all come from the same educational path. Perhaps I really <strong>do</strong> belong in this industry, and thanks to Ada Developers Academy, the landscape in which I am entering, is changing for the better every single day.</blockquote><p>Thus, I promise to not let those moments of self-doubt win. They will no longer get the best of me. I truly believe confidence comes from within and I’m on a mission to change the way I see myself. I’ll be taking it day by day but hopefully, those jokes about my intelligence are a thing of the past. TBD I suppose- I’ll keep you posted. 😉</p><h3>A few updates from my 2019 self:</h3><blockquote>March 2019:</blockquote><ul><li>I’m proud to say that not only did I continue to present &amp; give talks at local meetups in Seattle, but I went on to speak at TWO national tech conferences last year! And I’ve already got a few more lined up for 2019💣</li><li>I cannot confidently say that I fulfilled that promise to myself and made that day in May of 2018 the absolute <em>last </em>day that I made a joke about myself. But I can happily report that I <strong>no longer believe</strong> that I am not welcome in this industry. I have carved out space for myself. I now feel proud to be different and in fact, <em>love</em> sharing lessons and stories from my prior life as a teacher.</li><li>I’ve learned how to identify allies and mentors, how to ask the right questions in interviews of employers to identify teams that value diversity, and now am able to recognize managers who see my prior life experiences and unconventional path to tech as a benefit and not a detractor.</li><li>More importantly, <strong>I myself no longer see my path to tech as a handicap</strong>. I embrace the skills that I learned as an educator and have found ways to use them as assets in my new role as a Technical Product Manager. I am no longer embarrassed by my journey.</li><li>I’ll admit that while I sometimes still feel insecure about how much I don’t know, I’ve learned to reframe those thoughts and discover excitement in what I don’t know yet. Those unknowns are all just opportunities to learn more! The best part about this industry is that we get to be forever learners and can always find ways to challenge ourselves and learn something new.</li><li>Thus, in the past year, I’ve learned to embrace my failures as well as the many things that I do not know and understand them as opportunities to grow.</li></ul><blockquote><em>{ so long self-deprecation &amp; hello growth mindset! }</em></blockquote><p>I hope that by sharing this article, these insecurities, and the promises I made to stop defining myself by those feelings of self-doubt that I wrote to myself last year resonates with someone.</p><p>I hope that if you’re feeling alone, inadequate, stupid, insecure, or not welcome in this industry that this might help. I’m no longer embarrassed to admit that I sometimes feel that way too. Let’s start embracing what we don’t know. Let’s celebrate our unique paths to this industry and help create space for more to join in our wake and continue to diversify tech! 💪🏽</p><p>Follow my journey — @LoLoCoding 👩🏼‍💻 <a href="https://www.instagram.com/lolocoding/">Instagram</a> &amp; <a href="https://twitter.com/LoLoCoding">Twitter</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*n9YjlfYRsra-wIPDw8DiJw.png" /></figure><figure><a href="https://medium.com/swlh"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YqDjlKFwScoQYQ62DWEdig.png" /></a></figure><h4>This story is published in <a href="https://medium.com/swlh">The Startup</a>, Medium’s largest entrepreneurship publication followed by +434,678 people.</h4><h4>Subscribe to receive <a href="https://growthsupply.com/the-startup-newsletter/">our top stories here</a>.</h4><figure><a href="https://medium.com/swlh"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ouK9XR4xuNWtCes-TIUNAw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e7f53cdea20" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/i-swear-this-will-be-the-last-time-i-talk-sh-t-about-myself-9e7f53cdea20">I swear this will be the last time I talk sh*t about myself</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Good/The Bad of React & Redux: And Why Ducks Might Be The Solution]]></title>
            <link>https://medium.com/swlh/the-good-the-bad-of-react-redux-and-why-ducks-might-be-the-solution-1567d5bdc698?source=rss-b6d79fdd930a------2</link>
            <guid isPermaLink="false">https://medium.com/p/1567d5bdc698</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[redux]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <dc:creator><![CDATA[lauren lee]]></dc:creator>
            <pubDate>Sat, 19 Jan 2019 18:36:13 GMT</pubDate>
            <atom:updated>2019-01-20T12:12:21.791Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*S8GuQs4miAzpBbCzwNI4Vw@2x.jpeg" /></figure><p>Before I dive deep into the world of React and Redux, allow me to provide some context:</p><p>My journey to tech was rather unconventional or non-traditional if you will. I didn’t study Computer Science in college but actually was an <strong>English teacher </strong>for 7 years before embarking on my journey of learning to code.</p><p>During those years in the classroom, I spent a great deal of my time lecturing about structure. And by that I mean:</p><ul><li>the 5 paragraph essay</li><li>the art of writing an outline</li><li>rules of grammar</li><li>&amp; proper sentence construction</li></ul><blockquote><em>Essentially all things structure and organization when it comes to a high school lit class.</em></blockquote><p>This all combined with the fact that I’m also a Virgo means that I like <em>really really</em> like structure. Specifically, <em>organized structure.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/838/1*H0hvvXA2vLKwLpesyAdJRw.png" /><figcaption>Hi, my name is Lauren &amp; I’ll never not color code my notes</figcaption></figure><p>At <a href="http://adadevelopersacademy.org">Ada Developers Academy</a>, a tuition-free year-long program that trains women and gender diverse folk to code in Seattle WA, my peers were constantly giving me a hard time over my color-coded notes.</p><p>But in my defense, I had <em>just quit my job </em>and had taken this massive risk on learning to code, and this sort of stuff suits me! It brings me peace, joy, and sanity.</p><p>And while learning to code, just like my old classroom, I <em>loved</em> when everything had its place.</p><p>I love a thoughtfully organized codebase, it genuinely makes me smile.</p><p>So it should be no surprise that later on down the road when I became a software engineer at Amazon, I fell really hard for <a href="https://reactjs.org/">React</a>.</p><p>I’m sure a lot of readers may already know, but React has many powerful features including:</p><ul><li>the Virtual DOM</li><li>native compatibility</li><li>a relatively quick learning curve</li><li>helpful developer tools</li></ul><p><strong><em>but most of all:</em></strong></p><ul><li>the reusability of modularized components</li></ul><p>Ever since learning about it, I’ve always been really drawn to the component driven architecture that’s the foundation of React.</p><blockquote><strong>TL;DR</strong> React’s modular components are freaking awesome but sometimes state management can get wackadoodle</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wIQjDFk4iBryC5k68meTFA.png" /></figure><p>There are tons of articles/resources out there that provide details on <a href="https://tylermcginnis.com/reactjs-tutorial-a-comprehensive-guide-to-building-apps-with-react/">React’s awesome features</a> so I won’t dive deep into those here, but I will pause to make sure we’re on the same page when it comes to the modularized and reusable components.</p><p>When you build an app with React, you create a bunch of independent, isolated, and reusable components.</p><p>You then compose them all together to build complex user interfaces.</p><p>And the former grammar obsessed rule following teacher that I am LOVES the <strong>encouraged organization and division of the components this implies.</strong> I find the reusability of the components to be so helpful for engineers. Plus it always makes it so easy to find things within your code.</p><p>To visualize this concept, here’s a screenshot of a React app that aggregates viewing data to create a “Most Binged TV Shows” app:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0lA0PbRN_sxeeVHjyPsGcA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fHfscFb79ksWoPqw01MU8w.png" /></figure><p>The app itself can be divided into components:</p><ul><li>the nav</li><li>the show item</li><li>the show list all together</li></ul><p>The architecture of that app is pretty straight forward, but as we <em>all</em> know, things can get complicated and tricky and really quickly go from this to this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iyVFYdY26nnKMy-PyGs-Kg.png" /></figure><p>And thus developers at this point are forced to discover the sticky or <em>not so glamorous</em> part of React.</p><p>Oftentimes, developers want to pass state as props around the app quite a bit. React advocates for a single directional flow and things can get messy when you want to keep your data “in sync” when 2 (or more) components share that same data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sQX7BW98hfDW20FonHo8Kg.png" /></figure><p>Ideally, the source-of-truth of the data is only in one place. The React docs encourage you to <a href="https://reactjs.org/docs/glossary.html#state">“lift state up”</a> if you have two children that need to access the same data. This means putting the data in the nearest ancestor of the 2 components. But if these two components are very far apart in the tree, the “nearest ancestor” component could be at the TOP LEVEL of the component tree.</p><p>And to complicate things even more- the intermediate components may have absolutely <strong>NO USAGE for the props it’s being passed</strong>- it just happens to be stuck in the middle and has to pass it along. <em>No thank you.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WxjPzdw-gECIV4VzNkR3Ww.png" /></figure><p><em>My favorite analogy for this concept is the idea of me wanting to tell my cousin a story. But instead of being able to tell her directly that story, I also need to tell my aunt. Now that’s fine if it’s a little, non-embarrassing story, but say it’s about something I don’t necessarily want my aunt to know about?</em></p><p><em>Well, bummer dude, I still have to pass it through her regardless.</em></p><p>So the top ancestor has to pass the data down through several intermediate components along the way to get to the proper component, and just like the game telephone we played as kids, this creates a million different opportunities for developer error or unclarity for future users. The original story can get muddled and someone could easily get confused as they try to trace the props as they get passed between the many components.</p><blockquote>–aka no bueno-</blockquote><p>To view it another way, once state is being passed back and forth and up and down between the component trees, it’s easy to imagine that things could get <strong>complicated real quick.</strong></p><p>And to add insult to injury, my girl <a href="https://www.poodr.com/">Sandi Metz</a> taught me to<strong> fear coupling </strong>and that’s happening big time between each component and its parent. So to try and move a component around would become super complicated. There is coupling between the component and its parent AND between the component’s children that it’s passing props to!</p><p>Thus, to no one’s surprise, this impacts performance as every update to the data made will cause ALL of the children to re-render- which can cause massive performance and speed issues!</p><blockquote>🤷🏼‍So it’s really a balancing act. 🤷🏼‍</blockquote><p>There are many <em>great things </em>that React brings to the table, but as you can see, it’s important to find a solution for managing an application’s state if you’re hoping to build anything more complex than just a to-do list!</p><h4>When you’re in the designing phase of a project, more often than not, a few things are crucial:</h4><ul><li>for the app to be able to scale</li><li>to be able to create something that’s maintainable many months or years into the future</li><li>and dare I say, it’d be nice to maintain your sanity when it comes to state management!</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fgiphy.com%2Fembed%2FbvQeriB5VBjry%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fgiphy.com%2Fgifs%2Fgal-gadot-batman-v-superman-wonder-woman-bvQeriB5VBjry&amp;image=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fmedia.giphy.com%2Fmedia%2FbvQeriB5VBjry%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="180" frameborder="0" scrolling="no"><a href="https://medium.com/media/1c6bc78161c775edfda8660481d69ec3/href">https://medium.com/media/1c6bc78161c775edfda8660481d69ec3/href</a></iframe><h3>Which brings me to Redux- the state container superhero that saves the day!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TdBY1lsTYBgLlNChsniNAQ.png" /></figure><p>So, remember the chaos that was the mess of passing data around the components? That is what Redux successfully helps you make sense of.</p><p>Redux is a<strong><em> state management tool </em></strong>for JavaScript applications. Meaning that I can pass data <em>(or the embarrassing story about my most recent Bumble dating escapade) </em>to my cousin without having to also tell my aunt about it as well. Aka, I get to avoid the chaos of that story being bounced between all of the components (<em>or my many crazy uncles</em>), just to update or change one of them.</p><h3>And this all becomes possible because of Redux’s most important principle: the global store!</h3><p>So let’s talk about that. The big thing to remember is that the <strong><em>entire state of an application is stored in one central location</em></strong>, called the store.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2iqyOItGTjw-b5-Kw7Sshw.png" /></figure><p>Meaning that each component of your React app gets to have <strong>direct access to the state</strong> of the application without having to send props down to a child component or using callback functions to send data back up to a parent! And that’s pretty dreamy.</p><p>Redux provides a central store that can hold data from ANYWHERE in the application.</p><p>To put it differently, Redux completely eliminates this messy tunneling that can happen when you’re passing data from a parent down to many different subcomponents and manipulating it in all those places.</p><h3>Now, this is a diagram of how that all happens:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VKRRsTEk3A3jM6ZPEBQPBA.png" /></figure><p>And I’ll show how to add each piece of it to a React app to illustrate how it all works together.</p><p>So for the app I showed earlier, you can imagine that each color here is a different React component.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/1*Cz_4jr-pRwXFmVtFiYkOiw.png" /></figure><p>And currently with just React, the data in this app flows directionally as so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/1*Ugr8uwrPQA5vbzww9-u2jQ.png" /></figure><p>BUT I want to add redux so that the state and data transfer looks more like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tA1pTXB1_IUi6SAp-rjATw.png" /></figure><p>And to make that happen, the first thing to do is to build the store.</p><h3><strong>HOW TO ADD REDUX TO YOUR REACT APP</strong></h3><blockquote><strong>STORE</strong></blockquote><p>It’s crucial to remember that the store in Redux is like the<strong> human brain</strong>. It’s<strong> </strong>absolutely fundamental: <em>the state of the whole application lives inside the store</em>. So to start, you should create a store for wrapping up the state.</p><p>Create a directory for redux within your src folder:</p><pre>src/redux/</pre><p>Create a store folder within that:</p><pre>src/redux/store/</pre><p>Then create a new file named index.jsand finally initialize the store:</p><pre>// src/redux/store/index.js </pre><pre>import { createStore } from ”redux”;<br>import rootReducer from “../reducers/index”;</pre><pre>const store = createStore(rootReducer);</pre><pre>export default store;</pre><p>The createStore()is the function for creating the Redux store and while you may also pass an initial state to createStore(), most of the times you don’t have to. Although passing an initial state can be useful for server-side rendering, traditionally, <strong>the state comes from reducers</strong>, which is what I did here- it takes a reducer (rootReducer) as the first argument.</p><blockquote>BUT WAIT. I haven’t really explained what reducers do yet!</blockquote><p>Remember,<em> </em><strong>the state comes from the reducer</strong><em>. </em>What matters now is understanding what reducers do.</p><blockquote><strong>REDUCERS</strong></blockquote><p>Let’s go back to our diagram.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LQhwJC5V8i2_Giaa6XuCQg.png" /></figure><p>In Redux, <strong>reducers produce the state</strong>. The state is not something you create by hand.</p><p>Reducers specify how the application’s state changes. One of the principles of Redux is that the state is immutable and cannot change in place.</p><blockquote>In plain React, the local state changes in place with the function setState().</blockquote><h3>But in Redux, you cannot do that.</h3><p>A reducer is just a Javascript function- it takes two parameters: the current state and an action,<em> </em>which is why the reducer must be pure- meaning that it returns the exact same output for the given input.</p><p>And creating a reducer is actually pretty simple.</p><h4>Here’s how:</h4><p>Create a directory for the root reducer within redux:</p><pre>src/redux/reducers/</pre><p>Create a new index.js file within that folder.</p><p>In that file:</p><pre>// src/redux/reducers/index.js</pre><pre>const initialState = {<br>  shows: []<br>};</pre><pre>const rootReducer = (state = intitialState, action) =&gt; state;</pre><pre>export default rootReducer;</pre><p><em>This reducer is sort of a silly one because it returns the initial state without doing anything else.</em></p><p>But definitely notice how the initial state is passed as a <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Default_parameters">default parameter</a>.</p><h4>Now, reducers are without a doubt the most important concept in Redux. Let me say it again, <strong>Reducers produce the state of the application</strong>.</h4><blockquote>But this should then beg the question, <strong>how does a reducer know <em>when</em> to produce the next state</strong>?</blockquote><blockquote><strong>ACTIONS</strong></blockquote><p>Well, that’s where actions come in!</p><p>One of the principles of Redux is that the only way you can change the state is by sending a signal to the store. <strong>This signal is an action.</strong></p><p><strong>“Dispatching an action”</strong> is the process of sending out a signal.</p><p>And, how do you change an immutable state? <em>Well, you don’t. </em>The resulting state is a copy of the current state plus the new data.</p><blockquote>And you may be thinking, woah Lauren, that’s a lot of data to know.</blockquote><p>But the reassuring thing is that <strong>Redux actions are nothing more than Javascript objects</strong>! This is an example of what it might look like:</p><pre>{<br>  type: &#39;ADD_SHOW&#39;;<br>  payload: { title: &#39;Marvelous Mrs. Maisel&#39;, rank: 1, picture: &#39;https://image.jpg&#39; } <br>}</pre><h4>So let’s build the action</h4><p>Create a directory for the actions:</p><pre>src/redux/actions/</pre><p>Create a new index.jsfile within that folder</p><p>In that file:</p><pre>// src/redux/actions/index.js</pre><pre>export const addShow = show =&gt; ({ type: “ADD_SHOW”, payload: show });</pre><p>Every <strong>action requires a type property</strong> for describing how the state should change (and it’s really just a string). The reducer will use that string to determine how to calculate the next state. And you can specify a payload as I did if you like.</p><p>Referring back to the diagram and because types are just strings and strings are prone to typos and duplicates, it’s better to have action types declared as constants.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*N1pTYJUamnC22-RThFwncw.png" /></figure><blockquote><strong>ACTION TYPES</strong></blockquote><p>It’s a best practice to wrap every action within a function<strong> </strong>which definitely helps to avoid errors that would be difficult to debug.</p><p>So let’s also build a simple action-creator.</p><p>Create a directory for the constants within redux:</p><pre>src/redux/constants/</pre><p>Create a new action-types.js file within that folder.</p><p>In that file:</p><pre>// src/redux/constants/action-types.js</pre><pre>export const ADD_SHOW = “ADD_SHOW”;</pre><p>Then open upsrc/redux/actions/index.jsand update the action to use action types:</p><pre>// src/redux/actions/index.js</pre><pre>import { ADD_SHOW } from “../constants/action-types”;</pre><pre>export const addShow = show =&gt; ({ type: ADD_SHOW, payload: show });</pre><h4><em>Hold up, let me check in. Readers, are you still with me??</em></h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fgiphy.com%2Fembed%2FCURF5iPO5uY4U%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fgiphy.com%2Fgifs%2Fever-flawless-meryl-CURF5iPO5uY4U&amp;image=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fmedia.giphy.com%2Fmedia%2FCURF5iPO5uY4U%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="369" frameborder="0" scrolling="no"><a href="https://medium.com/media/058c4c545ed2aaad370a41c4f7c2520c/href">https://medium.com/media/058c4c545ed2aaad370a41c4f7c2520c/href</a></iframe><p>No? Okay maybe it would help, before going any further, if I recap the main Redux concepts and everything that just happened:</p><ul><li>the Redux store is in charge of orchestrating all the moving parts</li><li>all of the state lives as a single, immutable object</li><li>as soon as the store receives an action, it triggers a reducer</li><li>the reducer returns the next state</li></ul><h3><strong>The order sort of goes like this:</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WDvSOFIRLxJvBEydgdJsLA.png" /></figure><ol><li>An action first occurs within a component, such as someone trying to add a show, filter the view, see the details of a component, or even deleting a component, etc.</li><li>That then calls the action and action type</li><li>Which then grabs the particular reducer that will update or modify the state</li><li>And once the state is changed, the view is rerendered</li></ol><blockquote>Boom! And there you have it! That is how Redux works!</blockquote><p>Congrats! You now know <em>everything</em> there is to know about how to add Redux to a simple app and should feel ready to scale it to an app on your own. <br>Except, <em>wait</em>, you may have noticed that while I was setting up just the beginnings of the Redux architecture, I had to create a <strong>bunch</strong> of additional folders and files.</p><p>Now<strong> imagine adding in ALL of the functionality of a traditional app</strong>. If I was to continue down this path, it’d be easy to imagine how things could get pretty messy and/or confusing real quick.</p><p>You’d have to edit the constants in one file, then edit the reducer in another, then edit the actions in another, and finally, edit the action creators in yet another.</p><blockquote>It’s like a boring tennis match no one cares to watch!</blockquote><p>And it means that even adding just a small feature might equate to editing and adding several different files! <em>Which is kind of a headache.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fgiphy.com%2Fembed%2FEfEFcSNKrH70c%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fgiphy.com%2Fgifs%2Fcat-ping-EfEFcSNKrH70c&amp;image=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fmedia.giphy.com%2Fmedia%2FEfEFcSNKrH70c%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="326" frameborder="0" scrolling="no"><a href="https://medium.com/media/dc720bab7c93f8e93aa412f88473258b/href">https://medium.com/media/dc720bab7c93f8e93aa412f88473258b/href</a></iframe><p>This way of organizing your Redux is the most common and is essentiallyBy Type.</p><p>But as was just demonstrated, you end up hopping back and forth between files for a single piece of related functionality because the constants, actions, and action-creators are imported into the reducer file and the action-creators are also imported into the container to be dispatched. And all of this becomes a little annoying, wouldn’t you agree?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/426/1*09iYxYBxl5niQnOr-Mx3Hg.png" /></figure><p>What I found to be really wild was that there is actually no prescribed one way of organizing your Redux files. ThisBy Typemethod is super common and is taught in a ton of tutorials, but obviously, it’s sorta flawed.</p><p>My theory is that often times when you’re learning about Redux and the roles of actions and reducers, you start off with really simple examples.<strong> <em>And most tutorials available don’t take you to the next level.</em></strong> But if you’re building something with Redux that’s more complicated than a todo list, you realize pretty quickly that you may need a smarter way of scaling your codebase over time.</p><p>These actions, constants, and reducers are all related but are in a fractured state and honestly, switching from one file to the next not only takes a few seconds, but can make your head a little fuzzy, and<strong> I feel like it really slows down my production efficiency.</strong></p><blockquote>Simply put, it’s hard to maintain! 🙅🏼</blockquote><p>So obviously I felt frustrated by this when I was first learning React and absentmindedly set up an app’s architecture in this manner.</p><p>All of my English teacher organizational habits came rushing back to me. I KNEW that there was a way to strategic and thoughtful with the organization of a codebase’s architecture.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Ftenor.com%2Fembed%2F8631474&amp;url=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Ftenor.com%2Fview%2Floud-house-loud-house-gifs-nickelodeon-looking-for-something-gif-8631474&amp;image=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fmedia.tenor.com%2Fimages%2F1c728ce2e05aa84df9643fe8c73ad47b%2Ftenor.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=tenor" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/e1beaf0e8d38fc358810b9351f3bfc9c/href">https://medium.com/media/e1beaf0e8d38fc358810b9351f3bfc9c/href</a></iframe><p>I dove into the research and Medium articles knowing that there had to be something out there that would offer me some piece of mind. And I was right, there were lots of ideas out there about it.</p><p>Some people were suggesting online that a solution to this frustration might be to <strong>organize your code by feature.</strong> As in:</p><ul><li>encapsulating a component (the container)</li><li>its state (the store)</li><li>and its behavior (the actions) into a single folder</li></ul><p><em>All following the React’s component concept.</em></p><p>But this means that you’d have to <strong>tie a slice of the Redux store to a container </strong>and that is completely counterintuitive to the core of what Redux promotes!</p><blockquote>So I’m not about to advocate for this pattern to you.</blockquote><p>And so back to the drawing board I went and further research led me to ultimately discovering…</p><h3>The moment you’ve all been waiting for, based on the title of this article, <em>Ducks to the rescue!</em></h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fgiphy.com%2Fembed%2FUoLgC0VF7jDa0%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fgiphy.com%2Fgifs%2F90s-cartoon-gif-UoLgC0VF7jDa0&amp;image=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fmedia.giphy.com%2Fmedia%2FUoLgC0VF7jDa0%2F200.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="311" frameborder="0" scrolling="no"><a href="https://medium.com/media/ee81640b082601e024ce543161506c53/href">https://medium.com/media/ee81640b082601e024ce543161506c53/href</a></iframe><blockquote>But what are Ducks?</blockquote><p>Well, Erik Rasmussen, <a href="https://github.com/erikras/ducks-modular-redux">who coined the term</a>, realized that he was often creating and editing one piece of functionality at a time.</p><p>He kept needing to add {actionTypes, actions, reducer}tuples for each use case. Just as I was, he was keeping these in separate files and separate folders, however, 95% of the time, it was only one reducer/actionpair that ever needed their associated actions.</p><p>Thus, it made more sense for these pieces to be bundled together in an isolated module that’s self-contained and can even be packaged easily into a library.</p><blockquote>Ducks is essentially a proposal for bundling reducers, action types, and actions all into the same file.</blockquote><p>But <strong>WHY </strong>specifically would this organization structure be the solution to this architectural problem?</p><h4>Or rather, why get excited about Ducks?</h4><p>Beyond their adorable-ness factor that is 😉</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fgiphy.com%2Fembed%2FgVWMuKeB4PKMw%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fgiphy.com%2Fgifs%2Fsleeping-duck-gVWMuKeB4PKMw&amp;image=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fmedia.giphy.com%2Fmedia%2FgVWMuKeB4PKMw%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="408" frameborder="0" scrolling="no"><a href="https://medium.com/media/b5a7a41b4c13f2d812b7f584a05c30d8/href">https://medium.com/media/b5a7a41b4c13f2d812b7f584a05c30d8/href</a></iframe><p>Well, Ducks seeks to solve the issue of the toggled back and forth repetitive nature of organizing by type. With Ducks, rather than splitting up all related code, I can package it into redux modules!</p><h4>So let’s refactor the React app you just created and convert our Redux to DUCKS.</h4><p>Remember that the earlier example created the functionality of adding a show, and now you’ll need to move the actionTypes, actions,andreducers all into just one file!</p><h3>HOW TO CONVERT YOUR REDUX TO DUCKS</h3><ol><li>Create a directory for the Ducks within redux:</li></ol><pre>src/redux/ducks/</pre><p>2. Create a newindex.js file within that folder:</p><p>3. Grab the actionTypes from the constants folder and put it into the new ducksfile:</p><pre>// src/redux/ducks/index.js</pre><pre>export const actionTypes = {<br>  addShow: {<br>    ADD_SHOW = “ADD_SHOW”<br>  }<br>};</pre><p>4. Let the deleting begin and delete the entire constants folder!</p><p>5. Next up is actions file. Grab the actions:</p><pre>// src/redux/actions/index.js</pre><pre>addShow = show =&gt; ({ type: “ADD_SHOW”, payload: show });</pre><p>6. And put that into the ducks file:</p><pre>// src/redux/ducks/index.js</pre><pre>...</pre><pre>export const actions = {<br>   addShow = show =&gt; ({type: ADD_SHOW, payload: show});<br>};</pre><p>7. Continue the fun and delete the entire actions folder!</p><p>8. Lastly, tackle the reducers.</p><p>9. First grab this reducer:</p><pre>// src/redux/reducers/index.js</pre><pre>const initialState = {<br>  shows: []<br>};</pre><p>10. And actually, let’s change the reducer because the one from the first example does nothing other than returning the initial state, which is easy to fix by making it a switch statement.</p><p>11. In the ducks file add:</p><pre>// src/redux/ducks/index.js</pre><pre>...</pre><pre>export const rootReducer = (state = initialState, action) =&gt; {<br>  switch (action.type) {<br>    case ADD_SHOW:<br>    return { …state, shows: […state.shows, action.payload] };<br>    default:<br>    return state;<br>  }<br>}<strong>;</strong></pre><p>12. And of course, don’t forget to delete the reducer folder!</p><h3>13. TA-DA! You’ve just created a modularized Ducks file!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*rg3hVhOnazPu6_l7igO0qQ.png" /><figcaption>Your Ducks file should look a little something like this!</figcaption></figure><p>This file now officially <strong>contains ALL of the functionality that was built out before</strong>. It runs exactly the same way, but now, it is <strong>modularized into a clean, comprehensible file, <em>or duck</em></strong><em>, </em>for optimized state management.</p><h4>Just to really bring things home, remember when you created all of those folders and all of those files that you separated and fragmented from one another?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/516/1*sRkEaK0h0S2e6UZYppfKNQ.png" /></figure><p>Well, compare that mess to this new file, which contains all of that same capability in a legible fashion, and <strong>I’ll call that a win!</strong></p><blockquote>Plus, it’s pretty easy and painless to create.</blockquote><p>Thus, the art of ducks-ing is a way of structuring an app to become more modular, <em>which yes, is a real sexy buzz word</em> in the world of software engineering, but it’s really great because it now has become super obvious which piece of Redux is handling which functionality.</p><p>On a completely practical level, you no longer have to scroll through masses of files before finding the one you need to work on.</p><h3>But this is <strong><em>only one way</em></strong> of structuring redux. There are plenty of other options.</h3><p>And the simple fact that I’m encouraging readers to <em>explore ways to creatively define what might work best for you</em> may, in fact, mean that the structure-obsessed type-A person that I once was is leveling up to become someone who embraces ambiguity and discovers that sometimes you can define your own rules and doing whatever is best for your code and your team is ultimately the right choice!</p><h4>What I love most about Ducks is how clean and clear it is.</h4><p>It removes a lot of unnecessary boilerplate and you can easily add a simple action or even an app’s entire functionality by changing a single file.</p><p>I’ve been on teams that have adopted this structure and we were really happy with it.</p><blockquote>Maybe you will be too?!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l9-p862QALXZEawcfypZcQ.png" /><figcaption>Presenting at CascadiaJS 2018</figcaption></figure><blockquote>Give it a shot and let me know what you think.</blockquote><p>Hit me up on Twitter- <strong>@LoLoCoding</strong> and tell me all about your own quacky architectural solutions!</p><p>And be sure to check out <a href="https://github.com/erikras/ducks-modular-redux">Rasmussen’s</a> original proposal to learn more too!</p><p>Also, if you’re a visual/audio learner, here’s a <a href="https://www.youtube.com/watch?v=jr7D4VAzNig&amp;t=3s">video</a> of me <strong>presenting this information at </strong><a href="https://2018.cascadiajs.com/"><strong>CascadiaJS</strong></a><strong> in 2018</strong>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fwww.youtube.com%2Fembed%2Fjr7D4VAzNig%3Fstart%3D4%26feature%3Doembed%26start%3D4&amp;url=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttp%2Fwww.youtube.com%2Fwatch%3Fv%3Djr7D4VAzNig&amp;image=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fi.ytimg.com%2Fvi%2Fjr7D4VAzNig%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/26dc8dc646eb954363d9c492f22f9381/href">https://medium.com/media/26dc8dc646eb954363d9c492f22f9381/href</a></iframe><figure><a href="https://medium.com/swlh"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YqDjlKFwScoQYQ62DWEdig.png" /></a></figure><h4>This story is published in <a href="https://medium.com/swlh">The Startup</a>, Medium’s largest entrepreneurship publication followed by +413,678 people.</h4><h4>Subscribe to receive <a href="http://growthsupply.com/the-startup-newsletter/">our top stories here</a>.</h4><figure><a href="https://medium.com/swlh"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ouK9XR4xuNWtCes-TIUNAw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1567d5bdc698" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/the-good-the-bad-of-react-redux-and-why-ducks-might-be-the-solution-1567d5bdc698">The Good/The Bad of React &amp; Redux: And Why Ducks Might Be The Solution</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[So you’re new to coding? Tips on how to maximize your first month on the job.]]></title>
            <link>https://medium.com/swlh/so-youre-new-to-coding-tips-on-how-to-maximize-your-first-month-on-the-job-55372cd829fb?source=rss-b6d79fdd930a------2</link>
            <guid isPermaLink="false">https://medium.com/p/55372cd829fb</guid>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[codelikeagirl]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[code-newbie]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[lauren lee]]></dc:creator>
            <pubDate>Tue, 10 Apr 2018 03:51:03 GMT</pubDate>
            <atom:updated>2018-04-15T18:53:32.464Z</atom:updated>
            <content:encoded><![CDATA[<p>You’re the new kid on the block. You’ve got a sweet new backpack and the perfect first-day outfit all picked out. Congrats!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/355/1*o5XArWet5SOJ485SaHPInA.gif" /></figure><p>But all the preparedness in the world can’t mask the fact that you don’t know where or who to eat lunch with nor can it distract you from the small but persistent and haunting feeling that you may not actually survive day one. 😳</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*d7VY9gz2_0RQQl4IUD8Nww.gif" /></figure><p>I’m referring, of course, to the <strong>first day of a new job</strong>. (And while these feelings of anxiety may ring true across a variety of vocations, in this article, I’m referring to one in particular: Software Engineering.👩🏼‍💻)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ho7SQeQneag-geAv4Itn6w.png" /><figcaption>me on MY first day!</figcaption></figure><p>Not very long ago, I too was facing first day jitters of my own. And while I am by no means an expert and am in fact still quite a noob, I thought I’d write down a few notes before I become a big wig baller/coder extraordinaire who can no longer relate to feelings of inadequacy. 😂 I kid, I kid. No but seriously, while it’s fresh in my mind, I thought I’d put together some ideas on how to maximize and make the most of your time as a newbie.</p><p>Maybe it will be helpful for you? TBD, lemme know.</p><h3>How to ROCK the First Month of your Coding Job:</h3><ol><li><strong>Remember that the first day, or week, or month, or <em>whatever</em> for that matter, fears are NORMAL. </strong><br>It, <em>of course</em>, will feel as though everyone else has their shit together and that you’re the only one who has ever felt this way. But you’ll be <strong>wrong</strong>. And to prove it, I’ll share a few of the anxieties &amp; questions I asked myself throughout my first day (<em>that were only recorded because I insisted on writing literally everything down out of fear that I was going to miss a learning opportunity and thus some frantic emotions were recorded as opposed to legitimate notes on internal deployment systems or something like that — lol whoops — okay here I go</em>):</li></ol><blockquote><em>OMG am I the only woman on my team?<br>Shoot, do they ALL have Computer Science degrees? <br>Will they judge me for being a “bootcamp” grad? Oh god, </em>what<em> am I doing here? Do I deserve to be here? Definitely not. How did I con my way into this position? <br>Wait, where on earth is the women’s bathroom??<br>What is Kanban? Actually, what do </em>any<em> of those words that he just said mean? Maybe he’s speaking a different language? <br>Okay wait, that seriously feels like the 30th acronym he’s used in less than 5-minute time. <br>Oh no… does he think I am a college student?? <br>No, but seriously, you guys, </em>where<em> is the women’s restroom?</em></blockquote><p>As you can tell,<strong> fear and panic </strong>were dear friends of mine that day. And I document all of these questions &amp; fears not to pitifully expose my insecurities but to be honest that we all face self-deprecation and doubt sometimes. <br>Listen, it would have been VERY easy for me to succumb to that plaguing feeling of imposter syndrome and allow those negative thoughts to define me. I haven’t even been coding for a full year yet! And while some of those feelings may have been inevitable, I’m not going to apologize or feel embarrassed for having them or sharing them with you. This whole piece is an attempt to help those who are facing similar fears.</p><blockquote>So if you’re feeling unsure, or overwhelmed or terrified, you are not alone. And I don’t know if that helps to know that. But I think it would’ve helped me. So here on the list as #1 it stays.</blockquote><p>Let’s circle back to the part about me writing every little thing that happened down. No seriously, on page 3 of my notebook, just after I documented all of my first day questions, I drew a map of my team’s desk configuration and floor layout (<em>yes, including where the bathroom is</em>) including icons for each teammate based on the stickers on their computers. And while, okay, maybe that zoomed in version of ethnographic observation hasn’t turned out to be all that handy or helpful in the subsequent months, a lot of the note taking has in fact proven to be incredibly helpful! So that’s next on the list:</p><p>2. <strong>Be <em>diligent </em>in your note taking.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/1*UCvxuMybwPvii4_HLqaHDg.jpeg" /><figcaption>my trusty notebook</figcaption></figure><p>I’ve heard peers say that they were nervous to take too many notes during meetings out of fear of coming off as a noob. Buuuuuut let us not forget, we ARE noobs. And that’s nothing to be embarrassed about. There are too many unknowns to remember at the beginning. You need a place to keep track of it all- <em>so I say don’t go anywhere without your damn notebook. </em><br>And as standups continue to be peppered with unknown acronyms and words to this day, you better believe the moment I hear a new one I. write. it. the. eff. down. Who cares about looking dorky? It’s super helpful. Plus, I now have a beautifully scattered yet convenient glossary of words I used to not know! <br><br>3. Which actually brings me to, <strong>Lean into being the new person. </strong><br>Embrace it because before you know it, someone else will be joining your team and your excuse for not knowing how to do something because you’re the <em>new guy</em> will be long gone! Being new makes for a killer excuse to get to know people. Under the guise of being new, I scheduled one-on-one coffee dates with all the devs on my team during my first week. Each meeting turned out to be not only a great way to get to know them as individuals, but offered me time to learn more about their technical skills, passions, and expertise. To no one’s surprise, this was <em>really helpful </em>later down the road when I was blocked or confused &amp; needed help solving a very particular problem.</p><p>4. So, wait actually, maybe that’s one on its own: <strong>Ask everyone and anyone to coffee.</strong> It is so rare that people actually say no when you ask for 30 minutes of their time to chat. I started with my developer teammates, then expanded to the non-technical folks on my floor, and eventually I got brave enough to ask my boss’s boss for coffee. And when that went well, I went to their boss’s boss!</p><p>☕️☕️☕️☕️☕️ 🤓🤓☕️☕️☕️☕️☕️<br>I mean why not? I say, get a little ballsy because the worst anyone can do is no. Anyhow, this idea has really helped me build my network and learn about the company from a broader perspective. <br><strong>Tip</strong>: I usually have a set of questions ready to go if the conversation ever lulls. I’ve found that asking about a person’s path to tech is always a good bet. Not into coffee? We have frozen yogurt at my company, and there’s really no better way to bond, in my opinion, than over the mutual love of sprinkles AND code — Hello lifelong friendship! 🍦&amp;💻</p><p>5. On a more strategic note<strong>, Clump your questions by category </strong><br>Let’s face it, you are going to have a LOT of questions. It’s inevitable. You’re new! Write them ALL down and rather than shooting them off at your teammates in a sporadic rapid fire, be methodical about how and who you ask for help. Since you’ve just gone out to coffee with your teammates, you now probably have a pretty good idea of the work that they do and who is expert of what and thus you can direct your Java questions to one person and your deployment questions to another. That way, you aren’t constantly bombarding just one person with your confusions! Plus, you’re maximizing your time with each of them and demonstrating a respect for their interests and expertise! A win-win. 👍🏽👍🏽<br> <br>6. Beyond the average note taking, <strong>Keep a daily log of your achievements. </strong><br>I know I’ve harped on the importance of writing shiz down, but this is different. It is important to celebrate and document every achievement you have. We’re talking, even the teeny-tiny successes. It’ll come in handy when it comes time for evaluations with your manager, but it also helps when you’re feeling downright stupid or incapable of writing good code. In my personal wiki that I created to document my project (🚨nerd alert), I break down my notes by week and go as far as categorizing them into sections:</p><blockquote>Accomplishments<br>Blockers (and how I’ve solved them)<br>Key Concepts Learned<br>Areas of Progress<br>Areas for Improvement<br>Leadership Moments</blockquote><p>Everything is purposefully framed from a positive perspective — it works in a Jedi mind trick sort of a way to help me maintain that positivity.</p><p>7. Relatedly, I was also given the advice to <strong>Set a daily reminder to record these notes</strong> and so I will echo that here. I use the <a href="https://www.boomeranggmail.com/">Boomerang</a> app, which sends a prewritten daily email at 4:00 pm with a link to my Google form where I track these notes along with a word of encouragement that I wrote myself 3 months ago at the beginning of all of this.</p><p>8. <strong>Find mentors &amp; sponsors.</strong> And not just one. Definitely one for career and one for the more technical side of things. Consider someone, not on your team whom you can talk to about all things- both good and bad. There are a ton of articles that have been written more eloquently on this topic, so I will link to them at the end. But I don’t want to skip the importance of this. It’s quite literally imperative that you have someone in your life that can function as a sounding board during this time.</p><p>9. <strong>Lean in to your past experiences. </strong>What new lens can you bring to the table? Perhaps you have a new way of solving a problem your team is facing. Share that idea sister! Don’t hide that valuable life experience. Your perspective matters.</p><p>10. <strong>Don’t try to learn everything at once</strong>. Make a plan. Prioritize those milestones with your manager and taskify things so not to overwhelm or drown in the massive amounts of things you don’t know.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/282/1*SFb_bMubgnxaP6RbL8ZXtw.gif" /><figcaption>It’s easy to feel as though you have to learn everything all at once.</figcaption></figure><p>11.<strong> Remember, you just haven’t learned that <em>yet</em>! </strong>AKA, try with everything you have to keep the self-deprecation at bay. <br>It’s easy to feel like the dumbest person in the room. I get it. But I’ll call on my girl, Carol Dweck, right now and remind you of her whole <em>Growth Mindset </em>philosophy. Nothing good comes from beating yourself up for not knowing how to fetch data from the API. You do, however, have to <em>believe</em> that you have the tools to figure it out. You may not know how to do it right at this very moment, but you will eventually be able to get there. And that&#39;s what counts.</p><h3>So let’s change from I CAN’T DO THIS to I just haven’t gotten this YET! Shifting our mindset can really save the day sometimes.</h3><p>11. If you are a bootcamp grad or are coming to tech from a nontraditional background, <strong>DO NOT beat yourself up for being different. </strong>You are not doomed just because you don’t have a CS degree. You are a magical unicorn and you deserve to be here.🦄</p><p>12. Lastly, no matter who you are, <strong>you must believe that you can do this. </strong><br>No seriously, you can.</p><p><em>Confession time:</em> Just over a year ago, I was teaching my 7th year of English and was directing my kiddos in a teenager adapted rendition of Shakespeare’s <em>Twelfth Night</em>. Coding was still a pipe dream of mine. I pulled a major 180 in the life/career department, à la Miranda Hobbes shifting gears and running for governor, and if I can do this, YOU CAN TOO.</p><p>We cannot allow the things that we don’t know how to do (or code) to dictate our narratives.</p><p>So one last time, let me remind you: <strong>You belong. You deserve to be here.</strong></p><p>The opinions shared in this article are my own 💁🏼 — <a href="https://medium.com/u/b6d79fdd930a">@</a>LoLoCoding</p><p><strong>NOTE</strong>: While I <em>was</em> in fact the only woman developer on my technical team that day, I’m happy to report that as of 2 weeks ago, that is no longer the case! And <em>you better believe</em> I showed her where the bathroom was on her first day.</p><h4>Mentoring Links:</h4><p><a href="https://learntocodewith.me/posts/coding-mentor/">How To Find A Coding Mentor</a></p><p><a href="http://blog.flatironschool.com/your-ultimate-guide-to-finding-and-keeping-a-tech-mentor/">Your Ultimate Guide to Finding (and Keeping) a Tech Mentor</a></p><p><a href="https://www.girlboss.com/girlboss/2017/7/5/why-having-a-mentor-is-essential-to-your-success">Why Having A Mentor Could Be Essential To Your Success</a></p><figure><a href="https://medium.com/swlh"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YqDjlKFwScoQYQ62DWEdig.png" /></a></figure><h4>This story is published in <a href="https://medium.com/swlh">The Startup</a>, Medium’s largest entrepreneurship publication followed by 315,028+ people.</h4><h4>Subscribe to receive <a href="http://growthsupply.com/the-startup-newsletter/">our top stories here</a>.</h4><figure><a href="https://medium.com/swlh"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ouK9XR4xuNWtCes-TIUNAw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55372cd829fb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/so-youre-new-to-coding-tips-on-how-to-maximize-your-first-month-on-the-job-55372cd829fb">So you’re new to coding? Tips on how to maximize your first month on the job.</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Newbie’s Guide to Bug Bashing]]></title>
            <link>https://medium.com/swlh/a-newbies-guide-to-bug-bashing-2670da4b38f5?source=rss-b6d79fdd930a------2</link>
            <guid isPermaLink="false">https://medium.com/p/2670da4b38f5</guid>
            <category><![CDATA[code-newbie]]></category>
            <category><![CDATA[codelikeagirl]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[lauren lee]]></dc:creator>
            <pubDate>Fri, 16 Mar 2018 03:14:15 GMT</pubDate>
            <atom:updated>2018-04-23T03:17:49.958Z</atom:updated>
            <content:encoded><![CDATA[<p>This week has been hard. My code has been blocked literally since last Friday. And despite working with my mentor and other devs on the team, the problem lives on and every attempted build since has failed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/245/1*LXwRFEDPlwqXm57dJgk7nA.gif" /><figcaption>My relationship w/ my computer this week</figcaption></figure><p>And yeah… that has been pretty frustrating to say the least. It’s easy to get discouraged and feel defeated; to let imposter syndrome win and plagued by self-doubt.</p><p>But I’m not going to let it. Despite the frustration, this week has also offered me an opportunity to demonstrate a few things about myself.</p><p>It’s been a reaffirmation that I’ve got grit baby. I am NOT going to let this bug win. It will <em>not</em> <em>define me </em>as a developer or speak to my intelligence or about my ability to contribute meaningfully to my team. Facing such a confusing and complicated block in the code has not just exposed facets about myself as an engineer but who I am as a learner.</p><p>Upon reflection, I’ve realized that I systematically approached this block in a pretty methodical fashion-<em> </em><strong><em>aka I wrote an algorithm to tackle my code block</em>.</strong> And as I sit here reflecting on what can only be described as a bummer week, I thought I’d find the silver-lining by sharing that process with you all here.</p><h3>👾 <strong>Your Friendly Step-by-Step Guide to NOT Allowing that Tricky Bug in your Code Win 👾</strong></h3><ol><li>The first step is deciphering, decoding, and actually taking the time to <strong>READ</strong> and understand your error messages.</li><li>Next, begin researching other code bases and utilize any available resources (StakeoverFlow, Github, or perhaps a company’s internal wiki) to search for possible solutions. What have others done before you? There’s no need to reinvent the wheel here as your code is most likely <em>not</em> a unique and undiscovered snowflake of originality. Use your fellow engineers who have coded many solutions before you to your advantage!</li><li>Diligently record <em>all</em> generated possible solutions. Literally document every. single. idea. you. have. At this phase, there is no such thing as an idea too small or dumb.</li><li>Rank these solutions based on the likelihood of success and time it will take to implement (aka be smart with your time and don’t try the unlikely <em>and</em> burdensome solution first!).</li><li>Now, and <em>only now</em> do you get to coding! This is when you <strong>methodically</strong> attempt to implement the <em>best</em> possible solution that is at the top of your brainstormed list.</li><li>And if that solution fails <strong>(<em>it’s okay if it does</em>)</strong>, return to steps 1–4:</li></ol><ul><li>Repeat Step 1 and be sure to record whether or not you’ve received a new error message. There is information to be deciphered in both scenarios.</li><li>Repeat Step 2 and continue researching other examples based on those potentially new error stack traces, as you most likely now have new search terms to be googling.</li><li>Repeat Step 3 by reevaluating those possible solutions and adding new ones to the list if you can.</li><li>Repeat Step 4 if necessary, by smartly reranking the solutions based on that research, before trying a new one in step 5.</li></ul><blockquote>Essentially, you must be willing to continuously and cyclically refine and develop a more informed and zoomed-in list of potential solutions and continue chipping away at the problem. Just don’t give up! Stay persistent. The bug WILL NOT WIN.</blockquote><p>And it’s important to note that the problem <em>will</em> inevitably morph and change as you get iteratively closer to discovering the solution, and thus you must be open to that ebb and flow and resist the temptation to get discouraged. Remember, you can do this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q1yNmL7nrb1wqcdHmu_MNg.jpeg" /></figure><p>Seriously, why not switch the narrative? <em>Debugging</em> <em>doesn’t have to suck.</em> Maybe we could perceive each failure as a growth moment and an opportunity to deepen your understanding of the broader scope of the problem and codebase at large.</p><p>🎉Hooray new learning opportunities! 🎉</p><h3>SIDENOTE:</h3><p>Throughout the research process, you will inevitably discover other smart and clever ideas your code might benefit from that are perhaps separate from your current block. I would suggest recording those ideas and be willing to implement them periodically throughout the debugging process because it is no fun feeling stuck in the BLOCKED status all day every day. Plus it can be beneficial (and fun) to pull away from the problematic code, provide your brain some decompression time, and give yourself a win by implementing other (although potentially unrelated) positive changes every once in a while.</p><h3>So, is your bug fixed yet?</h3><p>Is your code flawless and ready for Code Review? Nope? <em>Yeah, me neither. </em>My stupid bug lives on. But at least I’ve found a way to spin what can be an incredibly negative and toxic experience into a relatively positive one! And for me, that feels like a win. 🤓</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/425/1*JnaV3NBhsNouRzdW18MD_A.gif" /><figcaption>Remember, #YouAreNotYourCode | Follow my coding journey 👩🏼‍💻@LoLoCoding</figcaption></figure><figure><a href="https://medium.com/swlh"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YqDjlKFwScoQYQ62DWEdig.png" /></a></figure><h4>This story is published in <a href="https://medium.com/swlh">The Startup</a>, Medium’s largest entrepreneurship publication followed by 307,492+ people.</h4><h4>Subscribe to receive <a href="http://growthsupply.com/the-startup-newsletter/">our top stories here</a>.</h4><figure><a href="https://medium.com/swlh"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ouK9XR4xuNWtCes-TIUNAw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2670da4b38f5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/a-newbies-guide-to-bug-bashing-2670da4b38f5">A Newbie’s Guide to Bug Bashing</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One year of Coding got me HERE]]></title>
            <link>https://medium.com/swlh/one-year-of-coding-got-me-here-99fc2bdfd3b8?source=rss-b6d79fdd930a------2</link>
            <guid isPermaLink="false">https://medium.com/p/99fc2bdfd3b8</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[girls-in-tech]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[lauren lee]]></dc:creator>
            <pubDate>Wed, 24 Jan 2018 02:34:50 GMT</pubDate>
            <atom:updated>2018-04-15T18:38:09.438Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Exactly one year ago, I had never opened my macbook’s terminal.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/852/1*Uwu-ALLSeXvwyhdCSIchGA.jpeg" /><figcaption>My image of a coder</figcaption></figure><p>And thanks to pop culture, I thought a <em>coder</em> was synonymous with a <em>hacker</em> and was someone who enjoyed working in a dark basement with massive headphones in a hoodie. I did not know a single web developer or anyone to counter or challenge that image in my head.</p><p>I was someone who couldn’t be further from that stereotype. I was an extroverted English teacher with a love for Shakespeare and Salinger, with a flair for theatrics, and a Masters in Teaching Liberal Studies. I could navigate Google for purposes of scholarly research and the occasional stalking of ex-boyfriends, but beyond that as well as my computer’s word processor, I was relatively un-savvy when it came to the world of tech.</p><p><em>Is it evident yet </em>that as of a year ago, I had<strong> 0.0 knowledge</strong> of what coding truly entailed? And yet, flash forward to January 2018, I am on the precipice of a major life change, am in love with web development, am about to begin a career as a software engineer, and things couldn’t be further from where they were back then.</p><p>Just a year ago, I had grown restless in my career and felt ready for a new challenge. I had met a few coding bootcamp graduates and was intrigued by the allure and the unknown world that is web development. The entire field itself felt unfamiliar and sort of sexy in its mystery. Despite the image of the antisocial coder that I had in my head, my curiosity had formed. I wondered:</p><blockquote>How does one build an app? What do coders actually do? But wait, how does the internet work?</blockquote><p>On a whim, I signed up for a free <a href="https://www.codecademy.com/learn">Codeacademy</a> course, which was an intro to HTML/CSS, I believe. I wasn’t sure that I would have the intellect or ability to learn it myself but the desire was there. I started attending local Seattle tech Meetups, trying to meet people in the industry, and began exploring what sort of opportunities were available to me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*3dPKz-shY1SmyHzxhzT2tQ.png" /></figure><p>Everything changed the moment a new friend told me about <a href="https://www.adadevelopersacademy.org/">Ada Developers Academy</a>.</p><p>Bootcamps felt out of reach, seeing as most range in cost from 10–20K, but she explained that Ada is tuition-free! I learned that Ada is a highly revered training program for women and gender diverse people who want to become software developers. It is unique from other bootcamps in that it is a year-long in length, which allows for genuine immersion into the learning process AND also guarantees a five-month technical internship afterward. To no one’s surprise, it is also incredibly competitive in regards to admission, so attending felt like a long shot. <strong><em>But I was hungry for it</em></strong><em>.</em> And the idea of attending a program that emphasized <em>collaboration</em> between students as opposed to <em>competition</em> was so dreamy to me that I became obsessed with getting in. It was quite literally all I talked about from January-March of 2017.</p><p>I threw everything I had into preparing and hustled my ass off for months until the application window opened. And I am not being superfluous when I say that my entire life changed on March 29th of 2017 when I opened my acceptance letter. <strong>I quit my job the very next day</strong> and left everything I had ever known behind.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yzNDfidK8DFGVSZb1odSMg.png" /><figcaption>I vividly remember opening this email while standing in line at H&amp;M to buy a pair of pants lol</figcaption></figure><p>As I approach the first anniversary of my pursuit of a career in coding, I thought it would be interesting to catalogue <strong>all the changes</strong> I’ve undergone in the past twelve months.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0cJqgzJ-Czs5AcOkgmqj5w.png" /><figcaption>Day 1 — Commute to School!</figcaption></figure><h3>So here it goes:</h3><p>1. As I mentioned, I picked up the hobby of aggressively attending Tech Meetups- as many as I possibly could find (sometimes 5+ a week!) in efforts towards building my network of developers and entrepreneurs- and quickly learned that while the field is dominated by males, there are many rad communities of women and folks who are working really fricken hard to change that fact and so many of which I now feel lucky to be a part of.</p><p>2. I left behind a job I loved and many amazing coworkers I had been with for the past SEVEN years</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*YjlsNo20LV3ZzfKJ8JaSWQ.jpeg" /><figcaption>Sonoma, CA — Feb 2017</figcaption></figure><p>3. Luke and I got engaged!</p><p>4. I, along with 47 other amazing and inspiring individuals, became apart of Cohort[8] at Ada</p><p>5. I began attending school again for the first time in a decade, which was mostly lecture-style, and literally went from 9–5 each day!</p><p>6. I read Sandi Metz</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3XBoTYF_uE4875WVhOURuw.jpeg" /><figcaption>my POODR notes and annotated book</figcaption></figure><p>7. I began to make friends and mentors within Seattle’s tech industry</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/536/1*iaX7cxRLrTa-1ZntOHThkA.png" /><figcaption>My coding buds</figcaption></figure><p>8. I learned Ruby, Ruby on Rails, HTML &amp; CSS</p><p>9. I became obsessed with Sandi Metz</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/584/1*80G4opcAGqzdHVjs4Fvrpg.png" /><figcaption>Me and SANDI METZ!</figcaption></figure><p>10. I attended RubyConf in New Orleans as an Opportunity Scholar where I learned that my community of coding friends does not have to exist just within Seattle (read more about that experience and my apparent love of writing lists <a href="https://codeburst.io/31-thoughts-i-had-while-attending-my-first-rubyconf-as-an-opportunity-scholar-eaa5d886bac0">HERE</a>)</p><p>11. I MET Sandi Metz!←</p><p>12. I learned that Java and Javascript are <strong><em>different</em></strong></p><p>13. Eventually learned <strong><em>what</em></strong> that <strong><em>difference</em></strong> is (special thanks to my industry mentor @mjdwitt who tried his best to hide his laughter when I asked him to explain it to me)</p><p>14. I competed in my first ever triathlon!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uvGv7Zl62AHAyfHOBnCJ_g.png" /><figcaption>My Cohort of Adies C[8]!</figcaption></figure><p>15. I learned that <strong>coding is by NO MEANS an independent or antisocial art </strong>and thrived during our class’ collaborative pair-programming and team-based assignments</p><p>16. I also learned that I am capable of working independently and problem-solving on my own when we were tasked to work alone on other projects</p><p>17. I learned how to consume and write my own API database</p><p>18. I applied for the <em>first time ever</em> to speak at a tech conference</p><p>19. I discovered the terror that is insomnia</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AnqWSgdLEC7prgGBnK9UCg.png" /><figcaption>My first ever Rails app!</figcaption></figure><p>20. I was <em>rejected</em> from said tech conference but that is <strong>NOT going to stop me</strong> from applying again next year!</p><p>21. I learned Javascript and Backbone</p><p>22. I built many MANY websites and applications in a variety of tech languages (checkout my Github repo directory <a href="https://github.com/laurenelee?tab=repositories">HERE</a>)</p><p>23. I learned to love (and also hate) Test-Driven-Development</p><p>24. I began learning the foundations of Computer Science (although, tbh I still don’t know what binary trees are/how they work… but we’re all a work in progress, right?)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ST_DALEtYcByEopK0bcBRA.png" /></figure><p>25. I cried in our school bathroom on more than one occasion / felt completely unworthy of receiving such an amazing opportunity of attending Ada / felt as though I must have tricked them into letting me in</p><p>26. I worked on my feelings of self-worth and with the help and support of fellow classmates and new Ruby friends, I eventually realized that I too deserve to be here</p><p>27. I learned the joys of refactoring and returning to sometimes just one-week-old code only to realize how awful it is and how much cleaner it could have been if only I had known what ternary operators are!</p><p>28. Luke and I got married down in Sayulita, Mexico along with 50 of our closest friends and family members in attendance</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ic2RasqB0DSgZLeVXXK0lA.jpeg" /></figure><p>29. I went through 3 massive notebooks filled to the brim with aggressively color-coded notes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/284/1*eaSnJ6rbbtR4paqd8zcW5w.gif" /></figure><p>30. I learned the importance of impeccable git-hygiene when I lost two day’s worth of work after my computer broke down</p><p>31. I began volunteering with <a href="http://seattle.chicktech.org/">ChickTech</a> to give back and encourage young girls that they TOO can succeed in STEM and the world of tech!</p><p>32. In prep for internships, I interviewed with 6 different tech companies, whiteboarded MANY algorithms &amp; DID NOT DIE</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3O2RLOeQvcuJxx7S14EQmg.png" /></figure><p>33. I judged a High School Hackathon where students actually believed that I myself was a coder!?</p><p>34.<em> Slowly but surely, I too began to identify as a coder</em></p><p>35. I officially completed the classroom portion of Ada!</p><p>36. I volunteered to support/help the NEXT batch of Ada students (fondly referred to as <em>Adies</em>)! Their cohort ( C[9] ) classroom portion begins next week! 😁😁😁😁😁😁</p><p>37. I was placed at my<strong> top choice </strong>for my internship, which will be with <em>Amazon’s Kindle Team</em>, beginning in February!</p><p>38. For my culminating <strong>Capstone Project</strong>, I taught myself React Native and wrote an iPhone app for teenagers in search of volunteering opportunities in just 3 weeks. Here’s a preview of the <a href="https://github.com/laurenelee/capstone-frontend-ReactNative/blob/master/README.md">VOLLEY</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/434/1*1woj9dnlFkAKfbXt0sHikA.gif" /><figcaption>To watch my presentation click <a href="https://www.youtube.com/watch?v=nfQDEmr37MM&amp;t=29s">HERE</a></figcaption></figure><p>39. Oh, last but certainly not least, we adopted a kitten and named him Dexter (and he is the best purr-programmer I’ll ever know)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/1*OHGF_4efYNlcDD4h6QWoBg.png" /></figure><p>40. AND bam! 💣 In just <strong>two days </strong>from this very moment, my classmates and I will be DONE with our Capstones and we will present our projects to our friends, families, instructors, AND future employers!</p><h3>Soooo… You could say things have changed just a little bit.</h3><p>This past year has not only been an intellectual renaissance for me, but in the process of learning to code, I have been encouraged to live more vulnerably than ever before and have discovered what amazing things can come from taking a risk.</p><p>I’ve learned that I grow so much more when I fail, as opposed to when I get something right on the first try.</p><p>While this year has been emotionally straining on my relationships, I’ve learned to savor my spare time and the importance of spending it genuinely and wisely.</p><h4>I’ve learned to bet on myself.</h4><p>I was someone who thought that the workings of a computer and the internet were that of magic, but now after understanding what’s going on under the hood, I’m even more in awe of its capabilities and aware of the power it has to connect people and create a better world than the one we live in.</p><p>While I at times may have questioned leaving my career as a teacher, I ultimately am so happy and proud to be a female entering the world of tech and as someone who is motivated to help make it a more collaborative, welcoming, and diverse space.</p><p>And with that, I’m off to tackle yet another year and to continue on my coding journey, which truly feels like a great and grand adventure. It reminds me of my favorite Dumbledore quote, which I will end on:</p><blockquote>“And now, Harry, let us step out into the night and pursue that flighty temptress, adventure.”</blockquote><h3>And be sure to check out the video presentation of my React Native iPhone app VOLLEY <a href="https://www.youtube.com/watch?v=nfQDEmr37MM&amp;t=29s">HERE</a>!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f0ndSgol48DZh-0vwLHR5g.png" /><figcaption>Thank for reading! Follow my journey: @LoLoCoding</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6gfnVvkMRFtjVsWF7vkClA.png" /></figure><h4>This story is published in <a href="https://medium.com/swlh">The Startup</a>, Medium’s largest entrepreneurship publication followed by 289,682+ people.</h4><h4>Subscribe to receive <a href="http://growthsupply.com/the-startup-newsletter/">our top stories here</a>.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6gfnVvkMRFtjVsWF7vkClA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99fc2bdfd3b8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/one-year-of-coding-got-me-here-99fc2bdfd3b8">One year of Coding got me HERE</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[31 thoughts I had while attending my first #RubyConf as an Opportunity Scholar]]></title>
            <link>https://codeburst.io/31-thoughts-i-had-while-attending-my-first-rubyconf-as-an-opportunity-scholar-eaa5d886bac0?source=rss-b6d79fdd930a------2</link>
            <guid isPermaLink="false">https://medium.com/p/eaa5d886bac0</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[retrospectives]]></category>
            <category><![CDATA[code-newbie]]></category>
            <dc:creator><![CDATA[lauren lee]]></dc:creator>
            <pubDate>Sat, 18 Nov 2017 17:13:52 GMT</pubDate>
            <atom:updated>2017-11-22T14:00:21.549Z</atom:updated>
            <content:encoded><![CDATA[<p>I am a full stack web development student @ <a href="http://adadevelopersacademy.org">Ada Developers Academy</a> in Seattle. I applied to attend RubyConf 2017 as an Opportunity Scholar (more info <a href="http://rubyconf.org/scholarships">here</a>). Below are some thoughts I had during my 3 days in New Orleans.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/572/1*P2X0eYZ4c14F618igPaxOQ.png" /><figcaption><strong><em>beignets</em></strong> @ Cafe Du Monde</figcaption></figure><h3><strong>Day 1:</strong><br>1. <em>Woah</em>, I’m scared. Do I deserve to be here? I do not know ANYONE here.</h3><p>#impostersyndrome #fakeittillyoumakeit</p><p>2. OMG, There is a line in the women’s bathroom!! This is a GOOD sign.</p><p>3. Matz says: “Ruby is nice so we are nice.” What a beautiful tagline. How incredible that Ruby was designed specifically to bring joy and happiness to its users? Thanks, <a href="http://twitter.com/yukihiro_matz">@yukihiro_matz</a> :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*o-wfexccX4Rr_wJNspadtQ.png" /><figcaption>Me freaking out when I ended up sitting in spitting distance of the creator of Ruby</figcaption></figure><p>4. Holy smokes <a href="http://twitter.com/railsCAMP">@railsCAMP</a> is a thing? I. am. in.</p><p>5. <a href="http://twitter.com/elieencodes">@</a>E<a href="http://twitter.com/elieencodes">lieenCodes</a> taught me how to identify open source projects to get involved in. This seems important. I’m declaring now to the internet that I am going to try my best and get involved.</p><p>6. Building off of that idea, <a href="http://twitter.com/_jnf">@_jnf</a> reminded me that using code for good is a beautiful, important, and tangible thing. I wept during his talk, but I am so glad I attended. After being a high school English teacher for so many years I struggle with the fact that I may end up at a company that does not necessarily contribute to the social good…</p><blockquote>“Not everything needs to be a product… use tech for good. Soothe problems for the ppl you love.” — Jeremy Flores</blockquote><p>Not all products directly correlate to making the world a better place and I get that. But I <em>do</em> know that when I search for projects to get involved in in the future, they absolutely will be those that I believe in.</p><p>7. Wow, developers LOVE stickers.</p><p>8. Damn, New Orleanian food smells amazing. Let’s create smellovision app to sync up TVs with odor tech.</p><p>9. My guide <a href="http://twitter.com/JessRudder">@JessRudder</a> is such a badass. This opportunity scholar/guide program is pretty incredible. Support, genuine kindness, and mentorship. We shared our stories with one another while eating delicious food or exploring the city together. Plus, sitting in the front row next to Sandi and Matz is pretty fricken amazing.</p><p>10. oOoOOoo! <a href="http://twitter.com/rubyforgood">@</a>R<a href="http://twitter.com/rubyforgood">ubyForGood</a> seems really fantastic. <em>TODO</em>: learn more about this event.</p><p>11. A developer evangelist and/or advocate sounds like a really cool job. #goals</p><p>12. This community can only be described as amazing.</p><p>13. Where does everyone put their stickers?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*MbwEe8quaRa1pDuWDnNixg.png" /><figcaption>Day 1’s sticker haul</figcaption></figure><p>14. Hearing Matz preview Ruby 3 is pretty darn exciting. It’s fun to learn what direction he and the core team sees the language moving in the future. #insidescoop! I’m sure a bunch of the stuff, like real keyword arguments and concurrency, will be really cool, but I think I’m too green to reaaallly understand those features. I do however understand that <strong>backward stack traces</strong> will be pretty great!</p><p>15. <strong>Networking tip received</strong>: hold your drink in your left hand so your right hand is free to shake! And always accept an offered sticker.</p><p>16. My running list of unknown terms to Google back in my hotel room is growing really really long.</p><p>17.<strong> Capstone project advice received: </strong>make it unique and quirky. Could help companies remember you and your project.</p><p>17. Everyone that worked on Apollo 11’s guides computer had no formal training? How rad is that? OMG and the original launch code is on Github? Fun. Thanks <a href="https://twitter.com/nateberkopec"><strong>@</strong>nateberkopec</a></p><p>18. People here seem really receptive to nontraditional paths to tech. No one seems to be judging me for not having a CS degree. In fact, people seem to be celebrating my prior life experience. I’m beginning to actually believe it when people say that it will help diversify the tech scene and be an asset to the community. 😊😊😊😊</p><p>19. Sooo apparently you can code music. <a href="http://twitter.com/samaaron">@samaaron</a> used a <a href="http://twitter.com/sonic_pi">@</a>S<a href="http://twitter.com/sonic_pi">onic_Pi</a> and live coded / DJ’d the <a href="http://twitter.com/digitalocean">@digitalocean</a> party. My mind was blown. Not only was it epic and technically interesting, it sounded great and was fun to dance to!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UgqiWUYWuiZbq40cJJx7NA.jpeg" /><figcaption>@samaaron’s Live code stream as he DJ’d the party</figcaption></figure><p>20. <a href="http://twitter.com/ChadFowler">@ChadFowler</a> encouraged us to rethink the connotation of the term legacy… W<em>ouldn’t it be pretty epic if Ruby was responsible for creating a “sustainable legacy”?</em></p><h3><strong>Day 2:</strong><br>21. Woah, I’m making friends! I’m learning so much… This is pretty fun!</h3><p>22. It’s the community. The open source team, the core, the people.</p><p>25. Life is short. Code will decay and betray you. Projects will die. People will die. So make the most of it while you’re here.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bs2uPCqrJKJjgPbz0FInnQ.png" /></figure><p>23. Might the sticker obsession be connected to <a href="http://twitter.com/AndyCroll">@AndyCroll</a>’s theory that everyone is a toddler? Feeling as though I should pull out my old sticker book collection from elementary school.</p><p>24. I can’t stop thinking about the tweet <a href="http://twitter.com/AndyCroll">@AndyCroll</a> referenced:</p><blockquote><a href="http://twitter.com/kyfast">@</a><a href="https://twitter.com/KyFaSt">KyFaSt</a> “Like most of you, I will be an average engineer. My legacy won’t be my code. It will be the names I lift up.”</blockquote><p>Mentorship, collaboration, support, teamwork, and allyship is essential in this field and in life.</p><p>25. If they don’t experience failure, a team becomes rigid, in fear of it. <a href="http://twitter.com/jessrudder">@</a>JessRudder reminded us all to learn from and embrace our failures.</p><p>26. <strong>More career advice received: </strong>find jobs that will fill gaps in my career. A generalist who is well rounded will go far.</p><h3><strong>Day 3:</strong><br>26. Hungover and headache. But #rubykaraoke was worth it. So was the piano bar where the original Sazerac was poured at 1 in the morning.</h3><p>27. Holy smokes, I really like all of my new friends. I have to come again next year to see them all again!</p><p>28. Gosh, I fangirled hard when I met <a href="http://twitter.com/sandimetz">@</a>S<a href="http://twitter.com/sandimetz">andiMetz</a>. I asked her to sign my copy of <em>POODR</em>. She is brilliant. And humble. Her keynote gave me all of the feels and when she said, <em>“You are good enough,”</em> I really believed her. All of her photos rocked by the way. Inclusive and representative. 🙌🏾</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/584/1*6FNLkMyHBxZciA-tJDVbIw.png" /></figure><p>29. Sandi’s stickers are pretty great.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U9xbCZIkdsKTh94tEX1NwA.jpeg" /><figcaption>Aaron’s face of pure joy while giving his ⚡️ talk</figcaption></figure><p>29. <a href="http://twitter.com/tenderlove">@tenderlove</a>’s talk encouraged me to question the assumptions I make when someone tells me something is impossible. Challenge accepted.</p><p>30. The sense of glee he demonstrated when he made Matz laugh while telling his hilarious story about the time his tweet went viral in Japan was seriously beautiful.</p><p>31. Maybe one day I could give a talk at RubyConf? Maybe I could try at a smaller scale at one of our local meetups to build up my skills and confidence.</p><p><em>And that’s a wrap. As I fly back home after what could only be described as a whirlwind of three days, I’m feeling all of the feels. That was quite literally so much more fun than I expected it to be.</em></p><h3>So I thought I would jot down some advice to future Opportunity Scholars or #RubyConf first timers.</h3><ol><li>Everyone should apply to be an Opportunity Scholar. Seriously. If you are new to the industry, a bootcamp student, a hobbyist, or even just slightly interested in ruby, you should do it. As of right now in my tech life/career, Ruby is all I know. And I feel so god damn lucky and happy that Ada chose to teach us this language first in their curriculum. I don’t identify as a strong coder yet but it didn’t stop me from having an amazing experience.</li><li>If you attend alone, know that you will survive and be okay. Everyone I introduced myself to was kind, asked questions, and was curious to hear my story. In fact, I am glad to have had the opportunity to go alone, despite how terrifying it felt at first. Yes, it is vulnerable making but it genuinely pushed me out of my comfort zone and each time I introduced myself to a stranger it got less and less nerve racking.</li><li>Ask for introductions from the friends you <em>do</em> make. My friend <a href="http://twitter.com/_havenn">@_havenn</a> introduced me to <a href="http://twitter.com/indirect">@indirect</a> and I am so excited to begin contributing to Ruby Together because of that moment of allyship and friendship.</li><li>Ask your guide and/or new friends what talks they suggest. It’s hard to judge for yourself which ones will be accessible to newbies and which will be too technical.</li><li>That being said, try to attend at least one talk that feels overwhelming, intimidating, or too techy for you. I attended a session on building a compact garbage collector and although a lot of it was over my head and my list of unfamiliar jargon to Google seriously doubled in such a short amount of time, but I now have a basic understanding of the subject! I have notes that I’ll be able to return back to in the years to come once I have a deeper knowledge on the topic. I won’t cower in fear of stupidity if the subject is mentioned at a meetup or in an interview. I can now hang in a conversation, not fluidly, mind you, but sorta kinda of 🤓</li><li>If you can and it sounds to you, run the 5k! It was a great way to see the city from a different vantage point and was a great opportunity to informally network/expand my circle of new friends. Thanks for being my running buddy, <a href="http://twitter.com/jeff_sacks">@jeff_sacks</a></li></ol><h3><strong>My retrospective:</strong></h3><p>I walked into this experience with zero expectations. I had never met anyone who had attended the conference before. Even after receiving the scholarship to cover the cost of my hotel, airfare, and the conference itself I was hesitant to attend. I was terrified of missing three days worth of curriculum @ Ada. Bootcamp life is hectic enough and three days can sometimes contain what feels like three weeks worth of knowledge and information. Even today, I missed an intro lesson on JavaScript on the browser and JQuery and literally thinking about that right now is causing me to break into a nervous sweat as I quite literally have no idea what JQuery is or does. 😳</p><p>But I can catch up on my school work and I will. I wouldn’t change a thing. This conference was so incredibly worth it. I learned about sweet gems, cool projects, and job opportunities. But more importantly, I met SO MANY totally epic and amazing individuals that even after only three short days I happily now consider friends. <em>I cannot wait </em>to follow their coding lives and journeys in the years to come. I am confident that so many of them are going to do great and groundbreaking things. Plus, I cannot WAIT for my next RubyConf.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DxAje2ZpgFXSwRg7mGgcdw.png" /><figcaption>drone selfie with other scholars &amp; guides @ Cafe Du Monde</figcaption></figure><p>Thank you again to <a href="http://twitter.com/jessrudder">@jessrudder</a>, <a href="http://twitter.com/stephanieblack">@stephanieblack</a>, <a href="http://twitter.com/_havenn">@_havenn</a>, <a href="http://twitter.com/thejonanshow">@thejonanshow</a>, <a href="http://twitter.com/geeksam">@geeksam</a>, <a href="http://twitter.com/jeff_sacks">@jeff_sacks</a>, <a href="http://twitter.com/zspenser">@zspenser</a>, <a href="http://twitter.com/jtu">@jtu</a>, <a href="http://twitter.com/betsythemuffin">@betsythemuffin</a>, <a href="http://twitter.com/rabbiGreenberg">@rabbiGreenberg</a>, <a href="http://twitter.com/EventsDoctor">@EventsDoctor</a>, <a href="http://twitter.com/CodeAndData">@CodeAndData</a>, <a href="http://twitter.com/valeriecodes">@valeriecodes</a>, <a href="http://twitter.com/rkofman">@rkofman</a>, <a href="http://twitter.com/sarahmei">@sarahmei</a>, <a href="http://twitter.com/chloecondon">@chloecondon</a>, and Ali, Yuna, Katy for making me feel like I belong in this community. Each of you demonstrated what advocacy, allyship, and friendship look and feels like. Thank you <a href="http://twitter.com/aphoenix">@aphoenix</a>, <a href="http://twitter.com/allie_p">@allie_p</a>, and <a href="http://twitter.com/KinseyAnnDurham">@KinseyAnnDurham</a> for organizing the Opportunity Scholar program. Your work is invaluable and I am beyond appreciative of all that you do.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eaa5d886bac0" width="1" height="1" alt=""><hr><p><a href="https://codeburst.io/31-thoughts-i-had-while-attending-my-first-rubyconf-as-an-opportunity-scholar-eaa5d886bac0">31 thoughts I had while attending my first #RubyConf as an Opportunity Scholar</a> was originally published in <a href="https://codeburst.io">codeburst</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>