<?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 Caryn Ligon on Medium]]></title>
        <description><![CDATA[Stories by Caryn Ligon on Medium]]></description>
        <link>https://medium.com/@CarynLigon?source=rss-207d8ae2b4e9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*rB8DjogV4ab4_dn3.jpeg</url>
            <title>Stories by Caryn Ligon on Medium</title>
            <link>https://medium.com/@CarynLigon?source=rss-207d8ae2b4e9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:28:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@CarynLigon/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[6 Ways to Make a Junior Developer’s First Year a Success]]></title>
            <link>https://medium.com/@CarynLigon/6-ways-to-make-a-junior-developers-first-year-a-success-426e97c3458?source=rss-207d8ae2b4e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/426e97c3458</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Caryn Ligon]]></dc:creator>
            <pubDate>Tue, 12 Jun 2018 16:54:50 GMT</pubDate>
            <atom:updated>2018-06-18T20:59:02.766Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/998/1*WU76i_8aYtFqfKAsQD7FLA.png" /></figure><h4>How to make those first months count</h4><p>I’ve been a front-end engineer at The Zebra since November 2016. This is my first job on an engineering team, so it goes without saying that I’ve learned a ton. I’ve reflected on the key factors that made my first year here successful and compiled a list of things to try if you are a team hiring junior developers or are one yourself:</p><h3>The team:</h3><h4>Create a safe place for asking questions</h4><p>Take the saying “there’s no such thing as a dumb question” seriously. It doesn’t matter how senior you are compared with the new junior; it’s important to be respectful to whoever has questions. The way a team responds to their coworkers’ questions plays a huge role in making the team feel safe and inclusive. It’s also important to ask questions in a way that respects everyone else’s time (more on that later), but we should be assuming the best of our coworkers and trusting that they’ve done their due diligence in trying to solve the problem on their own and truly are at a point where they need some help or a push in the right direction.</p><h4>Document processes</h4><p>Although it’s important to create an environment where employees feel safe and welcome to ask questions, providing opportunities to find answers on their own can be empowering and save them and the rest of the team a ton of time. New hires can start creating value right off the bat by reviewing and updating documentation of processes, features, etc. This benefits future hires and the organization as a whole.</p><h4>Set (not unreasonably) high expectations with enough support</h4><p>If you’re looking for junior hires who take initiative and are excited to learn and grow, you should have relatively high expectations that will challenge them and allow them to grow. As you do, provide as much support as you can to make these expectations attainable so new hires don’t get burnt out or discouraged.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kt1K61c9GpB2OoXloX22cA.jpeg" /></figure><h3>The junior developer:</h3><h4><strong>Try to figure something out first — but ask if you need to</strong></h4><p>This is a pretty tricky balance to strike. It’s important to show initiative and try and find answers yourself, but at some point, it’s good to lean on your team. You’re learning so many new things as a new junior developer — not only how to do your job, but also the domain (which for us at The Zebra can be a bit complicated since we’re dealing with car insurance). Your team’s documentation and onboarding processes can help set up new hires for success, but there will still be plenty of questions. Before asking, though, think about how you can make this whole process as efficient as possible. Scroll up or search in your team’s chat channel a bit. It’s likely that someone has had the same question before. If you do need to ask a question, include information about what you’ve already tried or learned and where exactly you’re getting stuck. The more detail and examples you can provide, the better.</p><h4>Don’t shy away from challenging work</h4><p>Having a super-supportive team really helps with this one, but have some faith in yourself. You were hired because someone (and probably multiple people) saw potential in you. Be realistic about your skill level, but push yourself to take on work that will get you out of your comfort zone. You’d be surprised how quickly you can learn new things.</p><h4><strong>If you have ideas/solutions — speak up</strong></h4><p>Always look for ways to add value to your team. If you have a new idea or a solution, bring it up. Even if it’s wrong, it’s at least a good opportunity to learn why it’s wrong. And no matter what level you’re at, you’re going to continue to say and do wrong things. They should become fewer and more far between, but there are always going to be times when you’re not 100% confident that the direction you’re going is the absolute best, but you need to make a decision and just get moving.</p><p>Your first year on an engineering team almost always goes by faster than you think it will. But those early days often set the tone for how you’ll work with the team from that point on. With some key support from your colleagues and a little initiative of your own, you’ll quickly be on your way to being a valued contributor.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=426e97c3458" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Authentication Fun with Firebase and Redux]]></title>
            <link>https://code.likeagirl.io/authentication-fun-with-firebase-and-redux-b5c191c03a85?source=rss-207d8ae2b4e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5c191c03a85</guid>
            <category><![CDATA[firebase]]></category>
            <category><![CDATA[redux]]></category>
            <category><![CDATA[codelikeagirl]]></category>
            <category><![CDATA[tech-talk]]></category>
            <category><![CDATA[react-native]]></category>
            <dc:creator><![CDATA[Caryn Ligon]]></dc:creator>
            <pubDate>Sun, 10 Sep 2017 22:21:17 GMT</pubDate>
            <atom:updated>2018-04-29T16:45:47.294Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/455/1*NirFAadC7H4x-N2QFOUZfg.png" /></figure><p>This is my first stab at writing anything somewhat instructional, so bear with me and please feel 100% welcome to provide any feedback and corrections. Also note that I struggled a bit to get this to work. It probably isn’t the most efficient or elegant solution, but it works! (again, suggestions welcome!).</p><p>My husband and I have been working on a nerdy mobile coffee app together the past few months. He’s been creating the designs while I’ve been building it using React Native, Redux, and Firebase. Here are the steps I followed to set up user authentication:</p><p><em>I’m going to fly through some of the Redux setup. There are a ton of great tutorials for setting all that up. I’m going to focus on creating Redux actions and reducers specifically for authentication, otherwise this post might turn into a novel.</em></p><h4>Step 1: Initial Setup</h4><p>Follow the “<a href="https://firebase.google.com/docs/web/setup">Before you begin</a>” section in the Firebase docs to create your app, get an API key, and copy your initialization code snippet that will look something like this:</p><pre>var config = {<br>    apiKey: &quot;&lt;API_KEY&gt;&quot;,<br>    authDomain: &quot;&lt;PROJECT_ID&gt;.firebaseapp.com&quot;,<br>    databaseURL: &quot;https://&lt;DATABASE_NAME&gt;.firebaseio.com&quot;,<br>    storageBucket: &quot;&lt;BUCKET&gt;.appspot.com&quot;,<br>    messagingSenderId: &quot;&lt;SENDER_ID&gt;&quot;,<br>};</pre><p>Then, install Firebase:</p><pre>npm install --save firebase</pre><p>I put that initialization code snippet from before into a settings.js file at the root level of my application and imported it as firebaseConfig into my main App component where I also imported and initialized Firebase:</p><pre>import React, { Component } from &#39;react&#39;;<br>import * as firebase from &#39;firebase&#39;;<br>import { firebaseConfig } from &#39;~/settings&#39;;<br>import { View } from &#39;react-native&#39;;</pre><pre>import { Signup } from &#39;~/pages/Signup&#39;;</pre><pre>let firebaseApp;</pre><pre>class Main extends Component {</pre><pre>    constructor(props) {<br>        super(props);<br>        this.state = {}; <br>    }</pre><pre>    componentDidMount() {<br>        firebaseApp = firebase.initializeApp(firebaseConfig);<br>    }</pre><pre>    render() {<br>        return (<br>            &lt;View&gt;<br>                &lt;Signup {...this.props} /&gt;<br>            &lt;/View&gt;<br>        );<br>    }<br>}</pre><pre>function mapStateToProps(state) {<br>    return state;<br>}</pre><pre>function mapDispatchToProps(dispatch) {<br>    return bindActionCreators(ActionCreators, dispatch);<br>}</pre><pre>const App = connect(mapStateToProps, mapDispatchToProps)(Main);</pre><pre>export default App;</pre><p>Cool, we’ve got a lot of the setup out of the way now. Let’s start writing some actions.</p><h4>Step 2: Authentication Actions</h4><p><em>Note: Since we’ll be making asynchronous requests to the Firebase API, we need to add some middleware. I was very confused about this concept for a while but </em><a href="https://codepen.io/stowball/post/a-dummy-s-guide-to-redux-and-thunk-in-react"><em>here</em></a><em> is a great tutorial that helped me a lot.</em></p><p>I have three scenarios to handle here:</p><ol><li>Make the request to the Firebase API with the user’s email and password</li><li>The request is successful and we receive some user data</li><li>The request fails and we need to alert the user</li></ol><p>This is the action that makes the initial request:</p><pre>export const createUser = (email, pass) =&gt; dispatch =&gt; {<br>    firebase.auth().createUserWithEmailAndPassword(email, pass)<br>    .then((resp) =&gt; {<br>        return dispatch(createUserSuccess(resp));<br>    }) <br>    .catch((error) =&gt; disptach(createUserFail));<br>}</pre><p>Let’s unpack this a bit. The initial function takes the user’s email and password that we’ve collected in the Signup component (and passed immediately to this function, don’t save that password anywhere!) as arguments. This function returns another function that receives the store’s dispatch method as it’s argument which then calls the <a href="https://firebase.google.com/docs/auth/web/password-auth">Firebase method</a> to create a user with an email and password. Finally, that function then dispatches the correct action based on the result of the request.</p><p>The createUserSuccess and createUserFail actions are more straightforward:</p><pre>export const createUserSuccess = (resp) =&gt; {<br>    return {<br>        type: CREATE_USER_SUCCESS,<br>        user: resp,<br>    }<br>}</pre><pre>export const createUserFail = (error) =&gt; {<br>    return {<br>        type: CREATE_USER_FAIL,<br>        error<br>    }<br>}</pre><p>If the request succeeds, we return the user data so we can save it to the application’s state and if it fails, we return the error so we can alert the user of what happened.</p><p>In the signup component, I’ve added an event listener to the simple email and password form that calls a “handlePress” function on the component which calls that initial createUser function. That function is made available through the component’s props by utilizing <a href="https://github.com/reactjs/react-redux">React Redux’s</a> connect binding:</p><pre>export default connect(mapStateToProps, { createUser })(Signup);</pre><h4>Steps 3: Updating the Application’s State</h4><p>The final step is to actually update the application’s state. We do this through a reducer which will return a new version of our application state with whatever data we need to add or change. Here is my authentication reducer:</p><pre>const auth = (state = [], action) =&gt; {<br>    switch(action.type) {<br>        case(CREATE_USER_SUCCESS):<br>            const { user: { uid: userId} } = action;<br>            return { ...state, loggedIn: true, userId }<br>        case(CREATE_USER_FAIL):<br>            const { error } = action;<br>            return { ...state, loggedIn: false, error }<br>        default:<br>            return state;<br>    }<br>}</pre><p>If the request was successful, I’m setting the user’s id to our state. If the request fails, I’ll set the error to the state so we can show some sort of descriptive error to the user.</p><p>There we have it! Users can now sign up to use the application! Firebase’s login methods are very similar to the sign up ones so I didn’t show that here. Once you get the gist of the registration process, you should be able to follow the same steps to add the login functionality.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3otPoS81loriI9sO8o%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Ffilmeditor-will-ferrell-elf-3otPoS81loriI9sO8o&amp;image=https%3A%2F%2Fmedia2.giphy.com%2Fmedia%2F3otPoS81loriI9sO8o%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/aea9d0db722893f74633627304b71152/href">https://medium.com/media/aea9d0db722893f74633627304b71152/href</a></iframe><p>VERY much a work in progress project with this in action: <a href="https://github.com/carynligon/Brew">https://github.com/carynligon/Brew</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5c191c03a85" width="1" height="1" alt=""><hr><p><a href="https://code.likeagirl.io/authentication-fun-with-firebase-and-redux-b5c191c03a85">Authentication Fun with Firebase and Redux</a> was originally published in <a href="https://code.likeagirl.io/">Code Like A Girl</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 Months Later]]></title>
            <link>https://code.likeagirl.io/ive-been-at-the-zebra-for-6-months-now-cc0094034307?source=rss-207d8ae2b4e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc0094034307</guid>
            <category><![CDATA[the-iron-yard]]></category>
            <category><![CDATA[codelikeagirl]]></category>
            <category><![CDATA[tech-talk]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[code-school]]></category>
            <dc:creator><![CDATA[Caryn Ligon]]></dc:creator>
            <pubDate>Wed, 31 May 2017 03:17:57 GMT</pubDate>
            <atom:updated>2017-06-01T13:21:50.331Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*9b49am7qwFHvllJXdPiVIw.jpeg" /></figure><p>I’ve been at <a href="https://www.thezebra.com/">The Zebra</a> for 6 months now. Which is crazy to me. Time has flown by. I’m grateful and feel really lucky that I ended up here. I had no idea what to expect when I walked in on day one but it’s been awesome. My team is supportive, hardworking, and a ton of fun. These past 6 months really have been amazing, but not without challenges.</p><h3>Challenges</h3><h4>Planning</h4><p>This has been the biggest challenge for me. In school, I got away with not spending too much time up front brainstorming and formulating a game plan for a new project. Most likely because I could change the project and go a completely different direction if I wanted to. That hasn’t quite been the case at work since I’m not tackling projects just by myself usually.</p><p>I’ve been trying to get into the habit of writing better design docs at work, sometimes even for smaller tasks that seem rather straightforward. There have been countless times where I jumped headfirst into a task, thinking I already knew exactly what to do. There have been almost an equal amount of times where that case has turned into quite the opposite and I’ve wasted time with an idea that never would have sounded good in the first place if I at least had written it down.</p><p>Spending a small chunk of time upfront can save you a bunch of time over the long run. And allowing others to see your thought process is super helpful for finding any holes in your plan or maybe somebody already wrote something that works the exact same way. Why waste that time? Move on to something else.</p><h4>Reading code that’s way better than your code</h4><p>This has been both a challenge and such a huge learning experience. Since I’m trying to stay organized, I’ll speak to the challenging side of it now (I planned out this post, can you tell?).</p><p>I just met JavaScript a year ago. We haven’t told each other our life secrets or gotten matching tattoos yet. I’m still trying to learn the ins and outs of JavaScript while it continues to change and new tools and libraries are constantly being built. There’s a new, cool way to write React components everyday. It’s hard to keep up with the new and improved way to write something when I’m still trying to wrap my head around what the reduce method does.</p><p>The people I work with have been doing this a lot longer. They’re way more familiar with the languages and just insanely smart. It’s discouraging sometimes to have to spend 5 minutes reading one function to figure out what might be going on. But, at the same time, that has been how I’ve learned the most over the past few months.</p><h4>Wait, what does this company even do?</h4><p>I’ve spent a lot of time and energy trying to overcome these challenges and so so many more that I’ve often lost sight of remembering to figure out what the company does.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FvIC9NVlVWvKBa%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fanimal-friendship-vIC9NVlVWvKBa&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FvIC9NVlVWvKBa%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="295" frameborder="0" scrolling="no"><a href="https://medium.com/media/4c6a1020144d3ce73e7d35e381b2619f/href">https://medium.com/media/4c6a1020144d3ce73e7d35e381b2619f/href</a></iframe><p>In order to fully understand the scope of a task or new project, I think it’s really important to also fully understand the business needs that it will satisfy. This has been extra challenging for me since The Zebra is a car insurance comparison company. I know little to nothing about any type of insurance.</p><p>Thankfully, The Zebra does an awesome job at acknowledging that a lot of people are pretty clueless about car insurance, including their employees and are dedicated to providing resources and time for teaching.</p><h3>The Good Stuff</h3><h4>Code reviews</h4><p>We didn’t really do this at <a href="https://www.theironyard.com/">The Iron Yard</a>. There’s so much curriculum and so little time so it’s understandable that we didn’t take a whole week to learn how to thoroughly read somebody else’s code.</p><p>Reading code reviews that have already been approved/rejected by other developers I work with has been extremely helpful. Whenever I have a spare few minutes, I’ll try and look through a few old reviews. Reading how others would have written something or how they interpreted a particular line has broadened the way I approach problem solving.</p><p>Obviously having my own code reviewed has also helped me grow a lot. To know how I could’ve written something more concisely or how I maybe forgot to consider a certain condition or that I spelled “vehicle” wrong 5 times has been extremely valuable.</p><h4>Persistence and confidence</h4><p>When I first started, I felt a bit of anxiety whenever I was just starting a new task and I initially had zero ideas for what to do and I would just assume that there was no way I was going to solve this problem.</p><p>Specifically over the past 2 months or so, I’ve felt so much less of that anxiety. I feel a lot more confident with what I know and what I don’t know, and therefore it’s easy to see where the holes are in a certain task that I need to patch together through googling, looking elsewhere in the codebase, or asking for help.</p><p>How I have approached tasks recently is saying “I’m not sure how to do this off the top of my head, but I can figure it out.” Going in with that mindset has made me way more persistent and positive throughout the whole process. Thinking about each task as a problem to be solved is way more fun and less stressful than thinking it’s some impossible task that’s way over your head.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FelDpPAkoxtnmE%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fdancing-tina-fey-elDpPAkoxtnmE&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FelDpPAkoxtnmE%2F200.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="317" frameborder="0" scrolling="no"><a href="https://medium.com/media/c339c3a44240c89a9eb370202cbb85fa/href">https://medium.com/media/c339c3a44240c89a9eb370202cbb85fa/href</a></iframe><blockquote>Going to a code school doesn’t magically make you a great developer or get you a sweet new job</blockquote><p>I talk to a lot of people who think of going to a code school to jump start a new career. I THINK THIS IS GREAT…but there is one stipulation: you need to like it. I am 100% on board with finding something new to do if you don’t like what you’re doing now. There are so many opportunities in such a variety of career paths right now. So many of us have the luxury to be able to choose our career path, so pick something you like, something you’ll work hard for and want to keep seeing how much you can grow in.</p><p><a href="https://www.codecademy.com/learn">Codecademy</a> has a ton of free classes available. Spend some time figuring out if you actually like coding and what you like about it before you jump head first into it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc0094034307" width="1" height="1" alt=""><hr><p><a href="https://code.likeagirl.io/ive-been-at-the-zebra-for-6-months-now-cc0094034307">6 Months Later</a> was originally published in <a href="https://code.likeagirl.io/">Code Like A Girl</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Little Late to the Resolution Party]]></title>
            <link>https://medium.com/@CarynLigon/a-little-late-to-the-resolution-party-995addfd46d5?source=rss-207d8ae2b4e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/995addfd46d5</guid>
            <category><![CDATA[new-years-resolutions]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[goals]]></category>
            <dc:creator><![CDATA[Caryn Ligon]]></dc:creator>
            <pubDate>Wed, 04 Jan 2017 04:48:44 GMT</pubDate>
            <atom:updated>2017-01-04T04:48:44.788Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s been a while since I’ve posted so here. Things have been busy at home with the holidays and I recently started a new job, so I kept mentally putting off this blog post. I will spare all of you the details of these past two months. The main event is obviously the job. I started at a company called <a href="http://thezebra.com/">The Zebra</a> about a month ago. The Zebra compares car insurance quotes from every top car insurance company to make picking the right policy as simple as possible — you should check it out.</p><p>I have learned so much, it’s a bit unreal. The people I work with are great and the company is just a ton of fun. I’m really happy how things have played out.</p><p>Anyway, the real purpose for this post is to essentially log the areas that I want to grow this year. I’d love to look back on this specific post next January and feel real good about it. Also, I’m pretty motivated by external pressure, so just knowing that maybe one or two other people know about these will help to keep me more honest.</p><p>I wanted to make these goals as SMART as possible, also to keep me honest. Here they are:</p><ul><li>Attend 6 live music events</li><li>Invest IRA this month and then contribute to it monthly</li><li>Run 3 times a week</li><li>Build something in real life (like with my hands and…tools?)</li><li>Learn one new skill to the level of semi-confidence</li><li>Donate money somewhere each month (more specifics TBD)</li><li>Volunteer each month at least once (I think I’m going to play this one fast and loose and just jump in whenever I hear about an opportunity)</li><li>Read 10 books (currently reading Animal Farm)</li><li>Cook at least 1 thing from all the cookbooks I own</li><li>Go to Japan (yep!!!)</li></ul><p>Well there they are. I’ve got a few more goals that are a bit more specific to my husband and I that wouldn’t make much sense here.</p><p>After fighting with this last paragraph about how to sum of my feelings of 2016 and the emotions I have going into 2017 with the coming political change, I have no better way to end this then just saying that I was too laid back about the things that excite me or make me furious in 2016. I want to be more aware in 2017, more relentless, and as involved and supportive as I can be.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=995addfd46d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bad words, good thoughts]]></title>
            <link>https://medium.com/@CarynLigon/bad-words-good-thoughts-583e6f036df5?source=rss-207d8ae2b4e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/583e6f036df5</guid>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Caryn Ligon]]></dc:creator>
            <pubDate>Thu, 03 Nov 2016 02:30:17 GMT</pubDate>
            <atom:updated>2016-11-03T02:30:17.737Z</atom:updated>
            <content:encoded><![CDATA[<p>These past few weeks have not been so great. Some things ended up not being what I thought they were and I was left quite a bit discouraged and melodramatic. I have recently kicked up applying for jobs into high gear, which is exhausting.</p><p>I’ve also started working on a concept for an app with my husband that we want to be mobile first, so I’ve started trying to figure out Xcode and Swift. I’ve also learned Angular and Redux. Needless to say, I’ve learned a ton in these past few weeks, which has ultimately led me to feel grateful for how things have turned out.</p><p>Sure, I’d love a job right now (seriously, right NOW), but I’m learning to be patient and how to reassure myself that I am competent and that I will find something. That sort of confidence hasn’t been my thing really ever. I continuously doubt myself and if things are good, I am convinced that they should be otherwise.</p><p>I don’t feel that now. I am confident in my abilities. I know that I will join a company and I will learn a ton. I also know that I will be an asset. I know that I work hard, am loyal and I learn fast. For some reason, timing isn’t on my side here but I am pressing on and trying to keep my chin up.</p><p>In the meantime…anybody have any resources they recommend for learning Swift and/or job openings they want filled?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=583e6f036df5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Baby Dev’s First Hackathon]]></title>
            <link>https://medium.com/@CarynLigon/baby-devs-first-hackathon-e66ccb6c631d?source=rss-207d8ae2b4e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/e66ccb6c631d</guid>
            <category><![CDATA[women-who-code]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Caryn Ligon]]></dc:creator>
            <pubDate>Mon, 24 Oct 2016 02:44:23 GMT</pubDate>
            <atom:updated>2016-10-24T02:44:23.239Z</atom:updated>
            <content:encoded><![CDATA[<p>This weekend was long and a little crazy. I participated in the 2nd annual Diversity Hackathon hosted by the Austin chapter of Women Who Code.</p><p>It was awesome. I went to happy hour on the first night with some friends from the Iron Yard. I made a promise to myself that I wouldn’t work with them. They are amazing people but I am way to anti-social and so needed to push myself to join a group of people I’d never met before.</p><p>My team was incredible. We worked on an application where you log what goals you’d like to achieve and based on those goals, you are added to a group with other people trying to achieve the same goal. From there, you can catch up with the group’s feed and learn about any tips from other members or see if anyone in your group is going to a relevant event in town.</p><p>Our application didn’t turn out perfect, we hit some road blocks, but I learned so much in just 3 days and had a ton of fun.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e66ccb6c631d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Not Writing Blog Posts]]></title>
            <link>https://medium.com/@CarynLigon/not-writing-blog-posts-d61abfc7e625?source=rss-207d8ae2b4e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/d61abfc7e625</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[3d]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Caryn Ligon]]></dc:creator>
            <pubDate>Sun, 02 Oct 2016 21:53:02 GMT</pubDate>
            <atom:updated>2016-10-02T21:53:02.570Z</atom:updated>
            <content:encoded><![CDATA[<p>For any of you who may have read my last post, you know that I’ve definitely failed at least one of my goals so far: blogging twice a week.</p><p>I’ve been trying really hard to keep myself on a strict schedule, but things happen, life gets a little messy and that’s ok. I’m not going to dwell on how many goals I’m not meeting, I’m just going to focus on getting closer and closer each week.</p><p>I almost can’t type my progress in job applications or interviews because I’m avoiding that this weekend since it’s the worst. I’ve applied to a bunch of places, I’ve had a couple interviews, I’m waiting to hear back…you know, normal stuff. This past Monday, I had a phone interview and coding challenge scheduled for 2pm, here is what happened:</p><ul><li>All last weekend — coding as much as I could and researching the company/position and thinking of questions I wanted to ask</li><li>Monday, 1:15pm — prep my interview station(aka my counter) since I’m paranoid and obviously need 45 minutes to have my pen(s) and paper aligned perfectly and my computer prepped and ready to go.</li><li>1:20pm — let dog out so he will be quiet during interview</li><li>1:30pm — make sure phone is not on silent</li><li>1:45pm — go get dog and bring him back inside</li><li>1:45:10pm — freak out because you locked yourself out of your house and no one is home and all your other doors and windows are locked.</li><li>2:00pm — miss your interview and contemplate your competence and overall success in life</li></ul><p>Not my best moment, I was sure that I had blown this opportunity. But then I discovered that people are kind and understand that other people are also humans and that this stuff happens.</p><p>I’ve still been learning D3 which I have grown to really, really, nerdily like. I am now trying to figure out how to incorporate D3 with React to build a health dashboard app. I just read <a href="http://oli.me.uk/2015/09/09/d3-within-react-the-right-way/">this article </a>by Oliver Caldwell and am starting to play around with <a href="https://github.com/Olical/react-faux-dom">react-faux-dom</a>, so we’ll see how that goes! I’m hoping to have this project finished by Friday so I should be sharing it in my next post, stay tuned!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d61abfc7e625" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Now what?]]></title>
            <link>https://medium.com/@CarynLigon/now-what-6aaa1b23293c?source=rss-207d8ae2b4e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/6aaa1b23293c</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[3d]]></category>
            <category><![CDATA[the-iron-yard]]></category>
            <dc:creator><![CDATA[Caryn Ligon]]></dc:creator>
            <pubDate>Mon, 12 Sep 2016 16:34:01 GMT</pubDate>
            <atom:updated>2016-09-12T16:34:01.391Z</atom:updated>
            <content:encoded><![CDATA[<p>I graduated from the Iron Yard two Fridays ago and had a final presentation for employers this past Thursday. Now it’s Monday and I’m sitting at a coffee shop keeping myself motivated to keep learning while applying for jobs.</p><p>This part isn’t actually that difficult for me. I’ve talked about how I feel toward job applications a few posts back. I am definitely more into the idea of camping out at coffee shops learning new frameworks and practicing what I learned while in school. Nevertheless, I need a job eventually, so I made some goals. For some added pressure on myself, I’ve decided to share them with the internet:</p><ul><li>Average 1 networking event per week where I meet at least 2 new people and ask anyone I find interesting to coffee/drinks</li><li>Code every single day for at least 30 minutes, but for a minimum of 15 hours per week. (AT THE VERY LEAST)</li><li>Apply for 15 jobs per week</li><li>Spend at least 5 hours searching for job opportunities</li><li>Blog twice a week</li><li>Oh and workout 4 times a week (I can’t just sit in front of my screen ALL the time)</li></ul><p>Some of these goals are going to be really challenging for me. Specifically the ones that involve job applications and networking. I made this list to be strict with myself and to hold myself accountable.</p><p>Also, here is what I’m doing/learning now in the coding realm:</p><ul><li>Recreating a to-do list app using React — one of our assignments was to make a to-do list app before we knew anything about user authentication and React. I’m a huge fan of lists as you may have noticed from this post, so I thought this would be a fun mini project to work on.</li><li>Learning D3 — this is proving to be difficult, but today I found <a href="https://www.youtube.com/channel/UCNYL0ZF2j8-OSGZ4iHBLNPA">this YouTube channel</a> that is teaching me D3 at about 2 mph, which is extremely helpful. I will be working on making some interactive charts/graphs for some designs my husband created once I’m up and running with D3, stay tuned for some examples! (Also, checkout my husband’s <a href="http://www.derrickligon.com/">stuff</a>, he’s a really talented graphic designer).</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6aaa1b23293c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Been a while…]]></title>
            <link>https://medium.com/@CarynLigon/been-a-while-2b9a6afd920c?source=rss-207d8ae2b4e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b9a6afd920c</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[life-lessons]]></category>
            <dc:creator><![CDATA[Caryn Ligon]]></dc:creator>
            <pubDate>Thu, 18 Aug 2016 15:20:17 GMT</pubDate>
            <atom:updated>2016-08-18T15:20:17.933Z</atom:updated>
            <content:encoded><![CDATA[<p>The past two weeks have been a bit crazy for me, hence the lack of posting. We are well underway on our final projects and having career sessions twice a week.</p><p>Talking about finding jobs, thinking about jobs, applying for jobs all make me want to crawl out of my skin. I don’t think I’m alone here. Trying to sell yourself is a weird concept for me. One of the main reasons I was drawn to programming was because it is something very tangible — I either do it or I don’t. Obviously there are varying degrees to which I can do this but my success is pretty easy to measure.</p><p>I got over this anxiety of feeling like actually getting a job as a front-end developer was unattainable a few weeks ago. I know I’ve learned concepts quickly and I that I will be able to keep up on an actual engineering team. However, trying to tell someone how great I am or whatever is weird. If I could hand someone a card with my github on it and run away and have it work out…oh I’d do it.</p><p>A few weeks ago, we got some worksheets about figuring out what our personal values and our personal mission statement are. I think remembering these things will be key for me when I start getting into the thick of job applications.</p><p>I know who I am and I know that I work hard and learn fast. More importantly, I know what matters most to me. Remembering these things helps me feel a bit better about going through this process. A job rejection doesn’t make me any less of a person or a developer, it just means it wasn’t the right job.</p><p>p.s. I’m super excited about the project I’m working on right now…stay tuned!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b9a6afd920c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Turning frustration into advocacy]]></title>
            <link>https://medium.com/@CarynLigon/turning-frustration-into-advocacy-6a776b7a8018?source=rss-207d8ae2b4e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a776b7a8018</guid>
            <category><![CDATA[the-iron-yard]]></category>
            <category><![CDATA[diversity-in-tech]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Caryn Ligon]]></dc:creator>
            <pubDate>Sat, 30 Jul 2016 16:34:32 GMT</pubDate>
            <atom:updated>2016-07-30T16:34:32.233Z</atom:updated>
            <content:encoded><![CDATA[<p>During our Friday huddle this week, we had two panelists talking about diversity in the industry and how we can play a part in being advocates ourselves.</p><p>I often find myself extremely frustrated that pay gaps and discrimination based on race, gender, sexuality…anything is still a thing honestly. However, thanks to the news and just hearing stories from others, I am reminded quite frequently that there are people who just don’t view this as a problem.</p><p>The panel was a good reminder that I don’t have to <em>just </em>be frustrated. But that I can take that frustration and turn it around and advocate for solutions to these problems.</p><p>The conversation really inspired me to make sure I ask about how companies value diversity and inclusivity in their workplace and product and to eventually get involved with teams that are promoting those values wherever I end up.</p><p>I know there’s a lot of people who feel similarly to the way I do. If we can learn how to wisely and respectfully speak up about these issues in our workplaces, I think we can make a big difference.</p><p>And for my ongoing list of what I’ve learned so far: this week was all about React. I am currently building a Jeopardy app using Backbone and React.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a776b7a8018" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>