<?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 Jami Gibbs on Medium]]></title>
        <description><![CDATA[Stories by Jami Gibbs on Medium]]></description>
        <link>https://medium.com/@jamigibbs?source=rss-ca0843dd0e42------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*LrSQJov4Rf0JZgQsb4kung.jpeg</url>
            <title>Stories by Jami Gibbs on Medium</title>
            <link>https://medium.com/@jamigibbs?source=rss-ca0843dd0e42------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 12:58:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jamigibbs/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[Getting Sass Running Quickly In Your React + Webpack Project]]></title>
            <link>https://medium.com/human-case-study/getting-sass-running-quickly-in-your-react-webpack-project-aa50ceba49c1?source=rss-ca0843dd0e42------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa50ceba49c1</guid>
            <category><![CDATA[webpack]]></category>
            <category><![CDATA[sass]]></category>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Jami Gibbs]]></dc:creator>
            <pubDate>Sun, 04 Nov 2018 15:10:51 GMT</pubDate>
            <atom:updated>2018-11-06T13:07:19.456Z</atom:updated>
            <content:encoded><![CDATA[<p>There are a lot of resources that explain how to add Sass to a React project using Webpack but many of them are complicated, assume a particular file structure, or are maybe focusing too much on optimization from the start. I found myself going round-and-round a few of those resources and all I was really looking for was the easiest possible way to get Sass running in a quick side project I was working on.</p><p>There’s just a few simple steps:</p><ol><li><strong>Install required NPM packages</strong></li></ol><p>There are three packages you’ll need to install for us to compile our sass file(s):</p><p>npm install style-loader css-loader sass-loader --save-dev</p><p><strong>2. Add the scss rule to Webpack</strong></p><p>In your webpack.config.js file, add a module rule for compiling sass with the previously installed packages:</p><pre>{<br> test: /\.scss$/,<br> use: [ &#39;style-loader&#39;, &#39;css-loader&#39;, &#39;sass-loader&#39; ]<br>}</pre><p>Your webpack config file might look a little different but here’s mine as an example. You can see that I’ve added a new scss test under the module key:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/63c0f8cdebe99d9dbdedfa06eb309b90/href">https://medium.com/media/63c0f8cdebe99d9dbdedfa06eb309b90/href</a></iframe><p><strong>3. Create your sass files and import them in components.</strong></p><p>In my situation, I just created a parent styles folder within my app and added a main scss file where I could put global styles:</p><p>app/styles/main.scss</p><p>Example app file structure:</p><pre>.<br>├── client<br>|   └── index.js<br>├── public<br>├── script<br>├── server<br>├── styles<br>|   └── main.scss<br>├── package.json<br>└── webpack.config.js</pre><p>For the global style, add your main scss stylesheet to the top of your project’s entry point. In my case, that was client/index.js. When we do this, those styles will get loaded down through the application components.</p><p>import &#39;..styles/main.scss&#39;</p><p>For individual components, create separate stylesheets and import it at the top of the component:</p><pre>.<br>├── client<br>|   └── index.js<br>|   └── components<br>|       └── navbar.js<br>|       └── navbar.scss<br>├── public<br>├── script<br>├── server<br>├── styles<br>|   └── main.scss<br>├── package.json<br>└── webpack.config.js</pre><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c325b5a2e2dbccf032b4b1ff6bb2ed9e/href">https://medium.com/media/c325b5a2e2dbccf032b4b1ff6bb2ed9e/href</a></iframe><p>That’s it!</p><h3>Conclusion</h3><p>Is there a more efficient way of doing this? Probably. Are there other opinions on how to structure your app or optimize the stylesheets? Likely. But if you’re just trying to put together a quick POC or have a fun side project you’re working on, these are three easy steps to get Sass, Webpack, and React working together quickly so you can keep moving forward with your project.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa50ceba49c1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/human-case-study/getting-sass-running-quickly-in-your-react-webpack-project-aa50ceba49c1">Getting Sass Running Quickly In Your React + Webpack Project</a> was originally published in <a href="https://medium.com/human-case-study">blog.jamigibbs.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Exposing Node Environment Variable to Handlebars Partials]]></title>
            <link>https://medium.com/human-case-study/exposing-node-environment-variable-to-handlebars-partials-d2e1364cc092?source=rss-ca0843dd0e42------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2e1364cc092</guid>
            <category><![CDATA[handlebars]]></category>
            <category><![CDATA[node]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Jami Gibbs]]></dc:creator>
            <pubDate>Mon, 17 Sep 2018 15:58:57 GMT</pubDate>
            <atom:updated>2018-09-17T17:45:37.488Z</atom:updated>
            <content:encoded><![CDATA[<p>The templating engine we use heavily in my work’s development team is <a href="https://handlebarsjs.com/">Handlebars</a>. Originally a fork of Mustache, Handlebars is fundamentally just a complier that takes in HTML and Handlebars expressions, compiles them to Javascript, and then inserts the resulting string into the relevant place on your HTML page.</p><p>Why bother using Handlebars if you can just write standard HTML then? I personally enjoy working with a templating engine because it allows me to create modular HTML that I can organize and reuse much easier. But more importantly, it decouples the logic (JavaScript) from HTML which can become difficult to read and manage so by using a logic-less templating engine like Handlebars, you can focus on just the HTML.</p><h4><strong>The Challenge</strong></h4><p>An interesting scenario brought up in our development team was how we could conditionally display a Handlebars partial based on Node environment (production vs development). A scenario where this might be useful is when a partial displayed some kind of Google tracking or other production specific analytics. We wouldn’t need to load that functionality in our dev environment so it might make sense to only compile those partials in production.</p><p>There are different ways you could set your Node environment variable but generally this would happen when starting up the environment. For example:</p><pre>&quot;start-dev&quot;: &quot;NODE_ENV=&#39;development&#39; npm run dev&quot;,<br>&quot;dev&quot;: &quot;gulp &amp;&amp; nodemon server.js&quot;,</pre><p>One of the things I mentioned earlier about Handlebars is that it’s logic-less. This means that it doesn’t have any explicit control flow statements like for loops or if conditionals. But it does allow looping and conditionals using built-in helpers. Here’s a simple example of a conditional:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2a556b6e2dadd7ffc00967ec2e5703dd/href">https://medium.com/media/2a556b6e2dadd7ffc00967ec2e5703dd/href</a></iframe><p>With that in mind, I started thinking about how we could pass our current Node environment variable (in our case either “production” or “development”) to a partial.</p><h4>A Solution</h4><p>One of the major ways that Handlebars differs from it’s predecessor Mustache is that it allows us to write custom helper methods that we can use with our partials.</p><p>With a custom helper we can add any type of Javascript logic we’d like but in this case, all I wanted to do was return a boolean value that told us if we were currently in a production environment or not. Since we’ve already set our NODE_ENV key value at start-up, we could register this relatively simple helper function that checks the value of that value:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9727c1236aeddc7265556945c4fa0051/href">https://medium.com/media/9727c1236aeddc7265556945c4fa0051/href</a></iframe><p>And applying our custom prod helper against the production only partial looked like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/18d842d6fb5b755d119b41df99d61467/href">https://medium.com/media/18d842d6fb5b755d119b41df99d61467/href</a></iframe><p>But an interesting thing happened when I tested this function. The #if conditional was not evaluating the returned value of the custom helper. It was always evaluating as false.</p><p>I theorized that either the values from our custom helper function weren’t returning as booleans, or, the built-in #if helper wasn’t evaluating the result of prod at all.</p><p>Testing the first theory, I created a second helper function to check the value’s typeof and confirmed it was outputting correctly:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/09e388bd8e8fdecaed7e9580ca311a73/href">https://medium.com/media/09e388bd8e8fdecaed7e9580ca311a73/href</a></iframe><p>For my second theory, I started experimenting with <a href="http://handlebarsjs.com/expressions.html#subexpressions">subexpressions</a> who’s purpose is to pass the results of one helper function to another. Take for example, the following using two helper functions:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c473bdd99dfcfc3f9c0a8477a2fdebde/href">https://medium.com/media/c473bdd99dfcfc3f9c0a8477a2fdebde/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b3e5150ef439fa5d30e32491a66e560c/href">https://medium.com/media/b3e5150ef439fa5d30e32491a66e560c/href</a></iframe><p>And this results in a string:</p><pre>Hello, Jami. How are you?</pre><p>Ok, so not super obvious how that’s useful in our case. The documentation doesn’t explicitly say this but my hunch was that I could use my custom prod helper passed as a subexpression using the parenthesis ( ) syntax which would then be evaluated by the built-in #if helper as a boolean value. How did I know this? I really didn’t! It was just a hunch that I was dealing with two helper functions that needed to talk to each other. So I gave it a shot and updated my partial:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2043d86b09e0b34a892552e3295d3bae/href">https://medium.com/media/2043d86b09e0b34a892552e3295d3bae/href</a></iframe><p>Now the conditional was evaluating the boolean value correctly! So when our Node environment variable is set to “production”, our view is rendering as:</p><pre>Seen only in production<br>This is some example text</pre><p>And when it’s set to something other than “production” it doesn’t render the partial which is exactly what we were trying to achieve.</p><h4>Conclusion</h4><p>The biggest hurdle here was that it wasn’t obvious how built-in helpers, custom helpers, and subexpressions played together. The Handlebars documentation don’t explicitly talk about how to handle boolean values passed to built-in helpers and it took some experimenting to figure out how to make that possible in this situation.</p><p>Thanks for reading! Follow me on <a href="https://twitter.com/JamiGibbs">Twitter</a> 👋🏼</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2e1364cc092" width="1" height="1" alt=""><hr><p><a href="https://medium.com/human-case-study/exposing-node-environment-variable-to-handlebars-partials-d2e1364cc092">Exposing Node Environment Variable to Handlebars Partials</a> was originally published in <a href="https://medium.com/human-case-study">blog.jamigibbs.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React Native & Geolocation: Finding Nearest Location]]></title>
            <link>https://medium.com/human-case-study/react-native-geolocation-finding-nearest-location-636b07236950?source=rss-ca0843dd0e42------2</link>
            <guid isPermaLink="false">https://medium.com/p/636b07236950</guid>
            <category><![CDATA[google-api]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Jami Gibbs]]></dc:creator>
            <pubDate>Tue, 19 Jun 2018 18:26:43 GMT</pubDate>
            <atom:updated>2018-06-19T18:27:05.719Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the weekend I <a href="https://github.com/jamigibbs/get-me-there-better">built a mobile app</a> to explore React Native and the mobile development process. While thinking about what I should build, I considered my own commutes and how I wish they could be better (I was likely commuting when I was thinking about it!). I take the train to and from Chicago’s northside to the River North neighborhood every day and I assumed city transit was the most efficient option by cost and time but I wasn’t certain.</p><p>So I set off to build an app that would provide multiple transportation options with a given location and destination and determine which of those options were better optimized for cost and time savings.</p><p>I assumed the user didn’t have a personal car (because I don’t) and that they could only use transportation options in Chicago. Those options are; train/bus, car ride sharing, bike sharing, and walking.</p><p>In the end, my app’s flow turned out to be as follows:</p><ol><li>The app displays the user’s current location and asks them to input a destination address.</li><li>With Google Location services, it autocompletes the destination address as the user is typing.</li><li>The app returns each transportation options including cost, travel time, and links to routes.</li><li>When the user toggles between “Cost Weighted” and “Time Weighted”, it marks the transportation option that’s optimized for that weight type.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*rNU2WiRQYnfqHqQKtI-hYg.png" /></figure><p>But in the process of building the app, I came across an interesting problem: how to find the nearest location from an array of locations? Specifically, I needed to find the nearest Divvy bike station from the user’s current location and provide them with a link to view the route to that station.</p><h3>Starting With Current Location</h3><p>At this point in my development, I already had available the user’s current location. This was accomplished by storing the geolocation provided by the user’s device (after the user granted permission, of course). The following snippet demonstrates how I accomplished this using <a href="https://docs.expo.io/versions/latest/sdk/location">Expo’s Location module</a> :</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/71cdc381ea42130d4ff8c3eee8316439/href">https://medium.com/media/71cdc381ea42130d4ff8c3eee8316439/href</a></iframe><p>I’m passing a boolean value into my getCurrentLocation thunk creator that allowed me to filter against the app being run in a simulator (which did not provide me accurate geolocation data). Then theLocation.getCurrentPositionAsyc promise returns the user’s location and dispatches it into to my Redux store.</p><p>If you’re not using Expo, you could also accomplish this with the <a href="https://facebook.github.io/react-native/docs/geolocation.html">React Native Geolocation</a> service. Using either method, the end result would be the same; access to the latitude and longitude values of your user’s current location.</p><h3>Dealing With Divvy Stations</h3><p>In Chicago, the bike sharing service <a href="https://www.divvybikes.com/">Divvy</a> has many hundreds of bike stations across the city. If I used the <a href="https://feeds.divvybikes.com/stations/stations.json">Divvy station public API endpoin</a>t, I would need to search through over 500 city locations before I could find the nearest station. That seemed woefully inefficient.</p><p>Instead of searching through every existing Divvy bike station individually, I could narrow it down to a search radius based on the user’s current location. After some research, I discovered that the Google Places API allows for just that using the nearbysearch endpoint and radius flag.</p><p>So now my request looked like this:</p><blockquote><a href="https://maps.googleapis.com/maps/api/place/nearbysearch/json?location=${lat},${lng}&amp;radius=1000&amp;type=point_of_interest&amp;keyword=divvy&amp;key=${API_KEY}">https://maps.googleapis.com/maps/api/place/nearbysearch/json?location=${lat},${lng}&amp;radius=1000&amp;type=point_of_interest&amp;keyword=divvy&amp;key=${API_KEY}</a></blockquote><p>The user’s current location was passed as lat and lng, with a search radius of 1000 meters, and all point_of_interest types for divvy returned. For any given location in Chicago, this query returns between 5–20 stations within a location radius. Not exactly what I was after but I was getting closer.</p><p>Of those stations within a 1000 meter radius, we could then check for a distance value from our current location against each station. To do this, I employed the help of the <a href="https://github.com/manuelbieh/Geolib">Geolib</a> library for distance calculations along with a couple of familiar Javascript array methods; map and sort.</p><p>I started with a thunk creator that received the user’s latitude and longitude for our Google places query:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/551c6140c10b2e9f46639b776a45ed31/href">https://medium.com/media/551c6140c10b2e9f46639b776a45ed31/href</a></iframe><p>The data returned from the GET request (using <a href="https://github.com/axios/axios">Axios</a> in this case) included an array of individual station locations. This gave me access to the latitude and longitude of each surrounding station but it came with a great deal of other information I didn’t really need in my Redux store. I only need the station’s latitude and longitude at geometry.location and eventually the distance from our starting point.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e6ededb9ac1bd708fcefb8c761482a02/href">https://medium.com/media/e6ededb9ac1bd708fcefb8c761482a02/href</a></iframe><p>I then used a map to go through each station and find just the latitude and longitude coordinates that I needed for each:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/aba9ce7ea6138a3303d4abf04fe28d58/href">https://medium.com/media/aba9ce7ea6138a3303d4abf04fe28d58/href</a></iframe><p>So now the station data looks like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c6d5b9934e01dc033c1578536695412f/href">https://medium.com/media/c6d5b9934e01dc033c1578536695412f/href</a></iframe><p>With each station coordinates, I could now calculate a distance value for each in the map and add that to my new array. By leveraging the Geolib library, I mapped over the location coordinates, calculated the distance value, and added that it to a new array of data:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f3d4f7f341cc2da4548b127d6f81f683/href">https://medium.com/media/f3d4f7f341cc2da4548b127d6f81f683/href</a></iframe><p>The resulting array after adding the distance value to each station location now looked like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a4aeaeb1d8147e87b63fdb624fe87e8d/href">https://medium.com/media/a4aeaeb1d8147e87b63fdb624fe87e8d/href</a></iframe><p>With our distances calculated, it was then just a matter of sorting for the closest station using the sort method and taking the first (closest) location:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/24a8772ce17e4ae437b5fa53cd57a690/href">https://medium.com/media/24a8772ce17e4ae437b5fa53cd57a690/href</a></iframe><p>Our Redux thunk that dispatches the closest Divvy bike station is now complete:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/db021bbbc49f5bc0656c86c9dbc50e1b/href">https://medium.com/media/db021bbbc49f5bc0656c86c9dbc50e1b/href</a></iframe><h3>Conclusion</h3><p>Working with API data can be challenging when you’re not getting exactly what you need to accomplish your task. But often you can solve the issue by working through the given data incrementally to transform it into the desired output. In this situation, the Google Places API allowed me to search within a specific radius area relatively easily but it took some creative data manipulation to be able to add a distance value as well.</p><p>Thanks for reading! Follow me on <a href="https://twitter.com/JamiGibbs">Twitter</a> 👋🏼</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=636b07236950" width="1" height="1" alt=""><hr><p><a href="https://medium.com/human-case-study/react-native-geolocation-finding-nearest-location-636b07236950">React Native &amp; Geolocation: Finding Nearest Location</a> was originally published in <a href="https://medium.com/human-case-study">blog.jamigibbs.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Fullstack Academy Application Experience]]></title>
            <link>https://medium.com/human-case-study/my-fullstack-academy-application-experience-534339aea482?source=rss-ca0843dd0e42------2</link>
            <guid isPermaLink="false">https://medium.com/p/534339aea482</guid>
            <category><![CDATA[fullstack-academy]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Jami Gibbs]]></dc:creator>
            <pubDate>Wed, 21 Feb 2018 20:28:25 GMT</pubDate>
            <atom:updated>2018-12-29T15:04:05.146Z</atom:updated>
            <content:encoded><![CDATA[<p>When I decided that I wanted to take a shot at the <a href="https://www.fullstackacademy.com/">Fullstack Academy</a> software development program, I had already done a lot of research. I read every Google search result I could find (I probably got 10 pages deep one day!). I looked at the Linkedin profiles of graduates to creep on their experience and employment after graduation (I reached out to a few of them too and everyone was incredibly friendly and helpful!).</p><p>I even setup a Google alert to email me when something new came online with the FA keyword and trawled through all of the Course Report reviews, Medium articles, blog posts, Quora responses, and everything in between.</p><p>In retrospect, besides the <a href="https://www.fullstackacademy.com/admissions">admissions material</a> on the Fullstack website itself, the most useful thing for me was reading the personal experiences of people who had gone through the process (both successful and unsuccessful candidates). Now that my application process has completed, I thought it would be a good opportunity to pay it forward to you, ambitious future Fullstack Academy applicant!</p><h3>Some Background</h3><p>It’s fair to say that I have some experience with coding already. I’ve worked in the web development field in some capacity for nearly 10 years. I’ve done WordPress development, website design, freelancing, and consulting. That translates to a lot of HTML/CSS, some server side stuff (PHP, SQL), some Javascript stuff, but no computer science. And I’m almost entirely self taught.</p><p>To gauge where I was technically at the time of my application, I would say that I could probably get through most of the <a href="https://www.codewars.com/">CodeWars</a> level 8 kata, some level 7 but starting to struggle, and probably not a single level 6 without Stackoverflowing the heck out of it. I had very specialized knowledge in WordPress dev, HTML templating, and graphic design which are great skills to have but there was some catching up to do if I wanted to transition into fullstack software development.</p><h3>The Why</h3><p>My decision to go back to school was the result of having a hard look at my career trajectory and realizing that it was taking me further away from my interests (coding!) rather than closer.</p><p>I first started researching Computer Science degrees a few months ago but ultimately decided it wasn’t a realistic option for my situation because it would have taken many years to finish and I wasn’t confident that I would be able to market my skills afterwards.</p><p>I was making a big decision and leap of faith to make this change so, if I was going to go to an immersive school, I had to 100% trust their program. It had to be focused on my long term success and I had to feel confident that it would give me the skills (and confidence) I needed to apply for the jobs that I wanted. The bottom line was that I had no time to waste.</p><p>The more I learned about FA, the more I felt like it was going to be my best chance at taking that leap from a website template creator that’s dabbled in JavaScript to a software engineer. The fact that they’re selective about who they accept into the program (some sources say the acceptance rate is ~8%) only made me more confident in the program. I knew that getting accepted was far from guaranteed but I wanted to give it a shot.</p><h3>The Application</h3><p>I had some vacation time during Christmas so I spent a week of that going through all of their <a href="http://prep.fullstackacademy.com/">prep exercises</a> and reading through Javascript resources. I was feeling pretty good about being able to solve most of the exercises so on New Years Eve, I sent in my written application.</p><p>The application itself wasn’t particularly long but I put in a good bit of time preparing my answers. I’m not sure how much weight it’s given in the overall evaluation process but they do measure candidates on a variety of criteria like educational/professional background and culture fit so I wanted to make sure those areas came through.</p><p>Something I’m also really glad that I did during this week was create a Github repo for my solutions to the exercise problems. I though it would be nice to reference my solutions later but I discovered that the real value was when I re-wrote all of those solutions during my 2nd prep stage. I could clearly see how I had improved on them looking at the diffs (example screenshot a bit further down). I was also able to use those diffs to highlight how I had improved throughout the application process and what my thought process was between the two solutions during the interview phase.</p><h3>Coding Assessment Exam</h3><p>The application process has three major phases:</p><ol><li>Written Application</li><li>Online coding assessment exam</li><li>Technical Interview(s)</li></ol><p>I sent the application on December 31st and I received an email on January 2nd inviting me to take the online assessment which was a much quicker response than I expected!</p><p>The exam was on the HackerRank platform with 6 problems of increasing difficulty (going from easiest to hardest). You’re given 75 minutes to complete them and once you begin, your browser goes fullscreen to deter Google-foo.</p><p>I won’t give details of those questions but I will give some tips:</p><ol><li>If you’ve never used HackerRank before, get familiar with it first before taking the assessment. This means doing actual problems on the platform to get a feel for how it works. This was something I wish I had done. You want to spend all your time focusing on the problems, not the platform.</li><li>I promise you’ll panic at some point but just breathe. If you don’t know the complete solution, start writing out your thought process into the editor. Let them see the steps you think might work even if you’re not sure how to code it. You can submit answers without the tests passing.</li><li>You’ll be able to go between questions without having a solution for the previous one so if you want to work on them out of order, go for it.</li><li>As part of your prep, practice timing yourself solving CodeWar problems (or similar) before the exam. This was my first experience being timed like that and it was terrifying. Practicing that format before probably would have helped me a lot.</li></ol><p>In the end, I think I was only able to complete three of the questions. For the other three, I wrote out possible solutions and ideas on how I might approach them but ultimately I simply ran out of time. Those 75 minutes go quicker than you think!</p><p>Not to be deterred, I still really wanted to know how to solve all of them so I spent a little more time after the exam working them out. I quickly found solutions to questions 4 and 5 (amazing how your brain starts working again when it’s not being timed) and sent them to admissions right away. I’m not sure if that really mattered in the end and I still wasn’t certain about the final question but I had a pretty good idea of what I needed to study up on. Surprisingly they wrote back that same day letting me know they were forwarding those final solutions to the assessment team so I was hopeful that I didn’t completely bomb it.</p><p>On Friday, January 5th, I completed the online assessment and on Monday, January 8th, I received an invitation to an interview. 🎉</p><h3>Technical Interview Part 1</h3><p>Everything was moving a lot faster than I expected. I scheduled my interview for the following Friday which left me about a week to prepare.</p><p>Even though I was invited to an interview, I was feeling a little less confident after the online exam so I studied more over that weekend reading about methods on arrays, recursion and working through more Codewars problems. In retrospect, I probably should have given myself more time to prepare especially since I was working full time on top of it all.</p><p>For the interview itself, we talked a little about my background and about the program itself. I had gone to one of their information sessions the week before where I was able to ask questions so I already had a chance to ask questions about the program.</p><p>Most of the interview time was spent working through two problems both I would rate as very fair assessments and relatively challenging. It took the entire hour for us to work through them both. The interviewer was really skilled at offering small guidance without giving the entire thing away but even with their excellent direction, it took some effort for me to work through them</p><p>In the end, I was able to find solutions to both but I had a nagging feeling that I wasn’t communicating my thought process well enough and my solutions weren’t exactly elegant or efficient (see O(n²) ). On top of that, it was my first live-coding / pair-programming experience so lots of nervousness and brain locks.</p><p>Honestly, I left feeling like I took a pretty good swing at it and thought that I demonstrated my potential although there were clear gaps in my knowledge and I was pretty lost when refactoring them to be more efficient.</p><h3>Technical Interview Part 2</h3><p>The same day, I got an email letting me know they’d like me to schedule a final round interview. They saw my potential but wanted to give me more time to study and prepare which, at the time, I didn’t quite understand so I asked for more feedback on my performance (and what I should be focusing on).</p><p>The feedback they gave was helpful but ultimately it was more about preparing myself more for the program itself from the <a href="https://www.fullstackacademy.com/admissions-preparation">material they recommend on their site</a>. They have a lot of experience with candidates and what it takes to be successful and, while initially disappointed that I didn’t get a green light straight away, I entirely trusted their judgement.</p><p>So for the next 4 weeks, I set myself to focusing on solving every problem I could get my hands on using only recursion or methods on arrays. I spent more time in Codewars land, going over the prep exercises again, and dug into the algorithms section of Free Code Camp.</p><p>It became clear to me how important this extra preparation time was when I pushed new solutions to the same <a href="http://prep.fullstackacademy.com/">prep exercises</a> I had done earlier. My improvements were clear:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h8boC437LgWcZ0B5XBVXRw.png" /><figcaption>4 additions and 18 deletions is a beautiful thing</figcaption></figure><p>When it came time to do the final technical interview, I was still super nervous (live coding is going to take some getting used to!) but I could communicate, debug, and work my way through the problem set a little easier than the first time around. I also felt like I had a bigger toolbox in general.</p><p>Two days after the final interview, I officially received my acceptance into the program. 🎉</p><h3>My Resources and Other Advice</h3><p>Stay positive. For some, this process might be easy and for others, it could take more preparation and patience. Just make sure that you’re hungry to learn and that you love what you’re learning before you dive in.</p><p>For someone coming from no background in code, they recommend studying 3–5 months before applying which is probably accurate. I have some experience already so I needed ~6 weeks to prepare. This preparation time will be different for everyone depending on experience and available time but it can be crucial. Don’t short yourself.</p><p>Some content specific advice would be to focus on algorithm exercises, array methods (reduce, map, etc) and simple recursion. Standard for loops are ok but you might want to have an idea on how to improve your solutions. Having a basic understanding of complexity (Big-O Notation) won’t hurt either.</p><p>My Tools and Resources:</p><ul><li><a href="http://flashcardhero.com/">Flashcard Hero</a> — Every time I came across a method on a function, array, string, number, or anything else I thought important to memorize, I made a flashcard for it. You don’t have to have everything memorized but you won’t be able to or have time to look things up while you’re going through the assessment test or interviews.</li><li><a href="http://eloquentjavascript.net/3rd_edition/">Eloquent Javascript</a> , 3rd Edition — I would recommend going through chapters 1 to 5 at a minimum but more wouldn’t hurt including the exercises at the end of each chapter..</li><li><a href="http://prep.fullstackacademy.com/">Bootcamp Prep Exercises </a>— Especially the Medium level set and try to do as many of them as you can <em>without</em> using for loops. Again, there’s not necessarily anything wrong with writing out your solutions this way but being able to talk about other approaches will be an advantage.</li><li><a href="https://www.codewars.com/">CodeWars</a> — Lots of level 8, 7, and 6 but go for higher if you can.</li><li><a href="https://www.freecodecamp.org/map">Free Code Camp </a>— The algorithms section was the most useful area for me.</li><li><a href="https://developer.mozilla.org/en-US/">MDN docs</a> — This is the only source I used when hunting down methods and examples.</li></ul><h3>What’s Next</h3><p>In the coming weeks, I’ll be working with their admissions team and will start preparing for the program (more studying!) as well as get financials and other things in order.</p><p>The entire process so far has been incredibly humbling and it’s made me realize how much more I need to learn. I fully expect every phase of the program to be challenging especially if the application process is any sort of measure for what’s to come.</p><p>Good luck if you’re reading this and have decided to apply too! Hopefully reading about my experience has helped!</p><p>Follow me on <a href="https://twitter.com/JamiGibbs">Twitter</a> 👋🏼</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=534339aea482" width="1" height="1" alt=""><hr><p><a href="https://medium.com/human-case-study/my-fullstack-academy-application-experience-534339aea482">My Fullstack Academy Application Experience</a> was originally published in <a href="https://medium.com/human-case-study">blog.jamigibbs.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>