<?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 Julianne Crawford on Medium]]></title>
        <description><![CDATA[Stories by Julianne Crawford on Medium]]></description>
        <link>https://medium.com/@julianne.marik?source=rss-6d9594b45309------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*wX9MuuKkMjD6WwF476yeYA.jpeg</url>
            <title>Stories by Julianne Crawford on Medium</title>
            <link>https://medium.com/@julianne.marik?source=rss-6d9594b45309------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 01:46:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@julianne.marik/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[Sequelize Associations & Magic Methods]]></title>
            <link>https://medium.com/@julianne.marik/sequelize-associations-magic-methods-c72008db91c9?source=rss-6d9594b45309------2</link>
            <guid isPermaLink="false">https://medium.com/p/c72008db91c9</guid>
            <category><![CDATA[association]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[sequelize]]></category>
            <category><![CDATA[magic]]></category>
            <category><![CDATA[relational-databases]]></category>
            <dc:creator><![CDATA[Julianne Crawford]]></dc:creator>
            <pubDate>Sat, 01 Dec 2018 21:50:41 GMT</pubDate>
            <atom:updated>2018-12-01T21:50:41.401Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*48kzVe-EZ7AfOldETv2Wig.png" /></figure><h3>Objective</h3><p>The objective of this article is to provide more understandable (visual) documentation on Sequelize associations and magic methods. If you’re new to Sequelize and/or relational databases, take a look at these articles (<a href="https://medium.com/@kimtnguyen/relational-database-schema-design-overview-70e447ff66f9">here</a> and <a href="https://milinaudara.wordpress.com/2014/05/24/an-introduction-to-sequelize-js/">here</a>) for some background information.</p><h3>Motivation</h3><p>When implementing a backend database, Sequelize is a powerful and effective object relational mapping (ORM) platform. Some of its capabilities, however, are obscured by pages of deterring and dense documentation. When I was first learning Sequelize, I struggled to understand model associations and their respective “magic methods”.</p><h4>Associations &amp; Magic Methods</h4><p>An association in Sequelize is a relationship between two models (a source and target model). Creating an association generally involves adding a foreign key to one model which creates a reference to the other. There are several Sequelize associations, including <em>has one</em>,<em> belongsTo</em>,<em> hasMany</em>, and <em>belongsToMany. </em>In terms of implementation, the key difference between these associations is in which model (the source or the target) the foreign key resides. I’ve made a series of visualization tools (see below) to help differentiate between these associations.</p><p>“Magic methods” are simply methods that are generated by defining Sequelize associations. As their name implies, the capabilities they invoke are quite magical. The visualizations below also outline which magic methods a given association will create. Alternatively, another way to easily see what magic methods a model has access to, is to use:</p><pre>Object.keys(ModelName.prototype)</pre><h3>Starting Point</h3><h4>Base Models</h4><p>For the purpose of this demonstration, I will begin with two base models — a parent and a child model. The tables below show how the 4 Sequelize associations mentioned above affect these base models, and what magic methods are created as a result.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/950/1*j3wdJKebBT1OPoapFfR85w.png" /></figure><h3>One-To-One</h3><p>One-to-one associations are between exactly two models connected by a single foreign key.</p><h4>Belongs To</h4><p>Associations where the foreign key exists on the<strong> source model</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lci7SZH17wz8aF5DwYY_qw.png" /><figcaption>One-to-One Association: Belongs To</figcaption></figure><h4>Has One</h4><p>Associations where the foreign key exists on the<strong> target model</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d8msBpBzf1Y24TS7sU8nWQ.png" /><figcaption>One-to-One Association: Has One</figcaption></figure><h3>One-To-Many</h3><p>One-to-Many associations connect one source with multiple targets. The targets however, are connected to exactly one specific source.</p><h4>Has Many</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uT2LZf1upseDWOiryFuOwA.png" /><figcaption>One-to-Many Association — Has M</figcaption></figure><h3>Many-To-Many</h3><p>Many-to-Many associations connect one source with many targets. The targets can also be connected to many sources.</p><h4>Belongs To Many</h4><p>Unlike the 3 previous associations, belongsToMany associations create a new joint table with the foreign keys of the target and source models.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hSOTKFg61dfS9WVQw487_g.png" /></figure><h3>Conclusion</h3><p>I hope these visualizations clarify the distinct differences between Sequelize associations and their corresponding magic methods. Once you understand these differences, Sequelize is extremely powerful in establishing relational databases and querying data.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c72008db91c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating a Mapbox React Component]]></title>
            <link>https://medium.com/@julianne.marik/creating-a-mapbox-react-component-1314d2796b7?source=rss-6d9594b45309------2</link>
            <guid isPermaLink="false">https://medium.com/p/1314d2796b7</guid>
            <category><![CDATA[react-components]]></category>
            <category><![CDATA[mapbox]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[built-with-mapbox]]></category>
            <category><![CDATA[redux]]></category>
            <dc:creator><![CDATA[Julianne Crawford]]></dc:creator>
            <pubDate>Mon, 12 Nov 2018 17:35:59 GMT</pubDate>
            <atom:updated>2018-11-12T17:35:59.595Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kL4gsjlHaeDorOweJ4MFBA.gif" /><figcaption>Tutorial Project — Mapbox &amp; React/Redux Integration</figcaption></figure><h3>Motivation</h3><p>My background is in Civil &amp; Environmental Engineering and I have a particular interest in creating beautiful and compelling data visualizations to impact urban development. I recently entered the world of programming which has allowed me to build upon this interest in a profound way.</p><p>I was working on a personal project, which involved fetching and mapping live data from Chicago’s CTA API, and decided to use the Mapbox-GL JS library to render my data. My application was built using Node/Express on the backend and React/Redux on the frontend. At first, it isn’t explicitly clear how to integrate the Mapbox-GL JS library into a React/Redux framework; therefore, I turned to a pre-built <a href="https://www.npmjs.com/package/react-mapbox-gl">React-mapbox-gl </a>component.</p><p>I found the pre-built component to be very powerful, but also quite limiting in specific instances. I decided it would be a productive exercise to create my own flexible React/Redux wrapper around Mapbox to understand the underlying complexities of maintaining a map’s style state when subject to user interactions.</p><h4>Disclaimer</h4><p><em>There are several other great articles (</em><a href="https://blog.mapbox.com/mapbox-gl-js-in-a-reactive-application-e08eecf0221b"><em>here</em></a><em> and </em><a href="https://hackernoon.com/react-redux-with-mapbox-78fa3767211e"><em>here</em></a><em>) that describe the process of integrating Mapbox GL JS into React applications.</em></p><h3>Aside - React/Redux</h3><p>In short, React is a Javascript library for building user interfaces. It is component driven and relies on the concept of state to update components and re-render the interface. Redux is a state-management library that emphasizes maintaining a single-source-of-truth over the state of an application.</p><p>Therefore, our initial question becomes what information might we need to maintain in the state of our Redux store? In mapbox, the “single-source-of-truth” of any map is its stylesheet which holds information about the map’s layers, sources, metadata…etc. The stylesheet is stored as an object, and can be accessed using a built-in Mapbox method: <a href="https://www.mapbox.com/mapbox-gl-js/api/#map#getstyle">map.getStyle()</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qqVUxapPaOdUuafCbOwiCg.png" /><figcaption>Mapbox stylesheet object</figcaption></figure><p>Therefore, we will store the stylesheet object in our state, and any time we want to modify the map, we will modify the state of the stylesheet directly and subsequently re-render the map component.</p><h3>Objective</h3><p>My objective is to build a simple React/Redux wrapper component around Mapbox. In order to demonstrate this process, I devised a simple example (see GIF above and <a href="https://github.com/juliannemarik/Mapbox-Wrapper">github repo</a>) which will serve as the end-goal of this tutorial.</p><p>This application is made up of two components: (1) a map component — which we will be building in this tutorial, and (2) a sidebar component which allows a user to interact with/alter the map’s style.</p><h3>Starting Point</h3><p><a href="https://github.com/juliannemarik/Mapbox-Wrapper/tree/startingPoint">githup repo</a></p><p>In short, we start with an App component which renders the Sidebar and Map components. The skeleton of the Map component has been set up, and the Sidebar component is complete, but has no user-interaction capabilities. The Redux store has been set up with an initial state, a reducer and action and thunk creators to fetch and set the initial data that we will be plotting as a layer on our map. In this case, we are pulling electric charging station data in Illinois.</p><p>You will need to install the following package to gain access to the Mapbox GL JS library</p><pre>npm install — save mapbox-gl </pre><h3>Process</h3><h4>1. Instantiate a Mapbox canvas in our Map component</h4><p>Using the mapbox-gl-js library, we can create a new mapbox object in our Map component. When we call this Map component from our App component, we will need to pass it several props (style, center &amp; zoom) to initiate the mapbox object. Note that in addition to container, style, center, and zoom, there are a number of other <a href="https://www.mapbox.com/mapbox-gl-js/api/#map">parameters</a> that could have been assigned.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2419b9b9d0b6ffbf2a9c36aef9ea659b/href">https://medium.com/media/2419b9b9d0b6ffbf2a9c36aef9ea659b/href</a></iframe><p>Once a new map has been instantiated, it has access to numerous <a href="https://www.mapbox.com/mapbox-gl-js/api/#map#scrollzoom">instance methods</a>.</p><h4>2. Add Sources &amp; Layers to Map Component</h4><p>Note: we could modify the initial stylesheet directly to add new sources and layers to our map; however, for the sake of this tutorial, we will simply use the built in map.addSource() and map.addLayer() instance methods before setting the initial style in our application’s state. Later, we will see how we can access the stylesheet to adjust the parameters of a layer and, in turn, modify the existing style state.</p><p>The layer we want to add to our map is a layer to show the locations of all the electric vehicle (EV) charging stations in Illinois. We will represent these locations with a circle marker.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5cde67b7bfde0f67cef1afc9da8d9065/href">https://medium.com/media/5cde67b7bfde0f67cef1afc9da8d9065/href</a></iframe><p>For more detailed information on how to add a source or layer, see the <a href="https://www.mapbox.com/mapbox-gl-js/api/">mapbox documentation</a>.</p><h4>3. Set the initial style state</h4><p>At this point, our “base map” is set up, and we’re ready to move on to our Redux store. We will need an action creator that accepts our map’s stylesheet, and a reducer which saves this updated stylesheet to our application’s state.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/12c80018139b4329a495f33353d7f6ac/href">https://medium.com/media/12c80018139b4329a495f33353d7f6ac/href</a></iframe><p>Back in our Map component, we can now dispatch the setStyle action with our initial stylesheet as the argument. We can access the stylesheet using the getStyle() method</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/53c97a5b928b86a5324adb98e27e5de7/href">https://medium.com/media/53c97a5b928b86a5324adb98e27e5de7/href</a></iframe><h4>4. Modify the state based on user interaction</h4><p>In this example, there are three user options we must consider. (1) water color, (2) EV stations, and (3) marker size.</p><p>When the user interacts with any of these controls in the sidebar, we want to modify the existing stylesheet to reflect their input. The process is generally the same in all three cases; therefore, for the sake of brevity, I will only go through the process explicitly for the water color case, but have made the entire repository available <a href="https://github.com/juliannemarik/Mapbox-Wrapper">here</a>.</p><p>In each case, we will set up an action creator in our store which, when dispatched, will traverse and update the state of the stylesheet with the new information we want to display.</p><p><strong>Changing Water Color</strong></p><p>Let’s start by looking at water color. When the user clicks any of the three color options, the color of the water in the map should change to that respective color.</p><p>Before setting up the action creator and reducer in our state, let’s take a look at the stylesheet. If you navigate into layers, you will find a layer called “water”. That sounds promising. If we expand this layer further, we will see that it has a paint property called “fill-color”. This property is controlling the color of the water, and is therefore the property we will want to change depending on what color our user clicks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uGFILpm0pucckiuYkSED5g.png" /></figure><p>Let’s go ahead and set up our action creator and reducer. Our action creator will take in a color, which our handler will subsequently set as the new “fill-color” of the water layer.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9d048456f7d74dd40070e568d1e1896b/href">https://medium.com/media/9d048456f7d74dd40070e568d1e1896b/href</a></iframe><p>Back in our Sidebar component, we can now set up a click handler which will dispatch this action to our Redux store and subsequently update our state with a new stylesheet.</p><p>Great! But we’re still missing one step. We’ve updated our store to reflect what we would like to see, but we haven’t actually updated the map with our new stylesheet.</p><h4>5. Update the map with a new stylesheet</h4><p>Back in our map component, we will need a new lifecycle hook to determine whether or not the state of our component has been updated. If it has, we will need to re-set the style of our map object with the new stylesheet on our state. we can do this using the built-in method map.setStyle()</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/fe12b5941950b4c73c974540e65a4a79/href">https://medium.com/media/fe12b5941950b4c73c974540e65a4a79/href</a></iframe><p>And that should do it! Now when the user clicks on a color in the sidebar, the color of the water should change as a direct result of the stylesheet being manipulated in our Redux store.</p><h3>Conclusion</h3><p>Building a React/Redux wrapper component around Mapbox gives you more flexibility and control over your application, and the process to do so is generally straightforward, relying solely on manipulating a map’s stylesheet. If you find yourself limited by a pre-built component, try following this process to build your own Mapbox Component. If anything, you’ll learn a lot from building the component from scratch, and you’ll walk away with a reusable component that can be used on future projects.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1314d2796b7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Applying To Fullstack Academy]]></title>
            <link>https://medium.com/@julianne.marik/applying-to-fullstack-academy-chicago-f87dbbc0bc41?source=rss-6d9594b45309------2</link>
            <guid isPermaLink="false">https://medium.com/p/f87dbbc0bc41</guid>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[codingbootcamp]]></category>
            <dc:creator><![CDATA[Julianne Crawford]]></dc:creator>
            <pubDate>Mon, 29 Oct 2018 03:19:06 GMT</pubDate>
            <atom:updated>2018-10-29T03:21:39.037Z</atom:updated>
            <content:encoded><![CDATA[<p>Chicago FSA 1809</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CaeIpe6vQ1onNe-1fXdnzg.png" /></figure><h3>My Background</h3><p>In March of 2018, I graduated from Stanford University with a M.S. in Sustainable Design &amp; Construction. My focus was in structures and sustainable urban systems.</p><p>Until recently, it was my intention to pursue a career in structural engineering, working at a design firm specializing in high-rise buildings and structural optimization. It became clear, however, that the time I enjoyed my work the most was when I was programming. I excelled in classes that used Matlab on assignments; I taught myself how to use Grasshopper, a visual programming language; I wrote my own structural analysis program using object-oriented programming techniques; and I designed and programmed my own personal portfolio website. During the final quarter of my M.S. degree, I decided to pursue this path and started researching bootcamps. At the time, I knew several people who had successfully completed bootcamps and supported the process.</p><p>My ultimate goal is to work as a developer at a company/organization that allows me to combine my backgrounds in civil engineering and programming. Civil engineering is a broad field, with opportunities in urban planning, renewable energy, infrastructure, and construction. These fields have unique possibilities when opened up to the world of programming, and I would like to be at the forefront of that development.</p><h3>Application Overview</h3><p>The application process is exactly as they outline it on their website:</p><ol><li>submit your online application</li><li>take an online coding assessment</li><li>have a one-on-one technical interview</li></ol><p>I originally applied to the Grace Hopper (GH) Track (in Chicago). After discussing the options with Chicago’s campus director, however, I decided to enroll in Chicago’s Fullstack Academy (FSA) instead.</p><p>Because Chicago doesn’t have its own GH campus yet, the main difference between the GH program and the FSA program is the deferred tuition model offered by the GH program. The website mentions that there are additional mentorship opportunities for women in the GH track; however, after speaking to Chicago’s director, he said these opportunities are available to all women on the Chicago campus, regardless of whether they are a part of the GH Track or FSA. Women who are a part of FSA do pay $2,000 less in overall tuition, however (although it is not deferred); therefore, after reflecting on the options in more detail, I decided to join the FSA program and pay the lower tuition of $15,610 upfront.</p><h3>My Application Timeline</h3><ul><li>Monday May 7th, 2018 @ 10am — submitted online application</li><li>Monday May 7th, 2018 @ 3:45pm — received an invitation to take the online coding assessment</li><li>Monday May 7th, 2018 @ 3:45pm — received an invitation to schedule a one-on-one technical interview</li><li>Wednesday May 9th, 2018 @ 12pm — completed the online coding assessment</li><li>Friday May 11th, 2018 @ 10am — completed my one-on-one technical interview</li><li>Monday May 14th, 2018 @ 8:30am — received acceptance email to join the September 2018 Chicago cohort</li><li>Wednesday May 16th, 2018 @ 11am — had a phone call with the Chicago campus directors to discuss the process moving forward</li><li>June 9th, 2018 — submitted the FSA enrollment agreement and the $2,000 deposit to secure my seat in the September 2018 cohort</li></ul><h3>Online Assessment</h3><ul><li>My online coding assessment consisted of 6 problems.</li><li>You are given 75 minutes to complete the assessment.</li><li>You have the ability to go back and forth between questions.</li><li>Each problem has a set of test cases that you’ll be able to run your code against, and it will tell you if they’ve passed.</li></ul><p>Before applying, I had taken an introductory programming class in Java and had a lot of Matlab experience; however, I had no prior experience programming in Javascript. I did the following to prepare for taking the online assessment in Javascript:</p><ul><li>I completed Fullstack’s online <strong>Bootcamp Prep</strong> with David and Nimit. When I was looking to apply, there was a promotional period for this new course, so I was able to take it for free. Normally this online course costs $175; enrolled Fullstack Immersive students are credited back this amount. The course took me about a week to complete (~ 40 hours total). The instruction was great, and the practice problems after each video were extremely helpful in increasing my proficiency with Javascript and preparing me for the online assessment.</li><li>In addition to the coding challenges in the prep course, I started drilling practice problems using <a href="https://www.codewars.com/users/sign_in"><strong>Codewars</strong></a>. I completed nearly 90 Kata — mostly 7kyu, some 6kyu and a few 5kyu. In my opinion, the online assessment is on par with most level 7kyu problems, and if you’re able to get down to 6kyu problems, you’re certainly ready for the assessment. Here is a good collection of <a href="https://www.codewars.com/collections/completed-7-kyu">7kyu</a> problems and a good collection of <a href="https://www.codewars.com/collections/completed-6-kyu">6kyu</a> problems to practice. Once you submit a kata, I highly recommend looking at other user’s solutions to the problem. This is one of the greatest features of Codewars, and offers a great way to learn new tricks and increase the efficiency of your solutions.</li><li>About a week before I planned to submit my application, I signed up for Fullstack’s free online <strong>Admissions Prep Workshop</strong>. I wanted to use this as a way to gauge my preparedness. The workshop was 4 hours, and was held via Zoom, an online meeting platform. During the workshop, we went over about 6 coding problems that were supposed to emulate the ones we might see on a typical coding assessment. For each problem, the instructor (a former student) gave us about 20 minutes to work through the problem on our own before he went over his own solution with the group. Another very helpful aspect of this workshop was that the coding platform we used to solve the problems was identical to the one you’ll use to take the assessment.</li></ul><p>With this preparation, I felt more than ready for the online assessment. I was able to get through all 6 problems and pass all of the given test cases. With that being said, don’t worry if you aren’t able to! At the very least, write down your thought process, and don’t get caught up on any one problem. You can always go back to it if you have extra time at the end.</p><h3>One-on-one Interview</h3><p>My one-on-one interview was with one of the FSA instructors and lasted for an hour. Overall, the interview was very laid back, and followed the exact format outlined by founder, Nimit, in this <a href="https://www.fullstackacademy.com/blog/how-to-ace-the-fullstack-academy-interview">article</a>:</p><ol><li><strong>Introduction</strong> — My interviewer asked me a few questions about myself and my objectives in applying to the program. He then discussed the key elements of the program, explaining, in depth, the 3 phases — foundations, junior phase, and senior phase.</li><li><strong>Programming</strong> — This made up the majority of my interview and consisted of 2 pair-programming questions. Using a shared platform, I walked my interviewer through how I would solve these problems. If you prepared for the online assessment, I’d say there’s no additional preparation needed to be able to solve these problems. They may be slightly more difficult, but your interviewer will guide you/answer any questions you may have along the way. I would, however, highly recommend practicing talking/reasoning through a problem out loud before your interview. Whether it’s with a friend or by yourself, it’s really helpful to take a few problems from Codewars (or any other platform), and as you’re typing out your solution, talk through your thought process. This is what your interviewer will be evaluating, and even if you aren’t able to get a working solution right away, it will show your interviewer that you know how to reason through a problem. To settle everyone’s nerves, neither of the problems I was given <em>required</em> recursion; however, the second problem <em>could</em> have been solved using recursion and my interviewer encouraged me to solve it both ways for him. If you’re looking for some additional recursion practice, I’d recommend working through a few problems from this <a href="https://www.codewars.com/collections/recursion-1">collection</a> on Codewars.</li><li><strong>Q/A</strong> — Following the pair-programming portion of the interview, we had a few minutes remaining for me to ask any questions I had about the program and the process moving forward. Make sure you write out a few thoughtful questions before your interview.</li></ol><h3>Final Thoughts</h3><p>I’m about to start senior phase at Fullstack and have loved everything about my experience. The quality of teaching, the structure of the curriculum, and my fellow peers have all exceeded my expectations. If you’re looking to make the jump, I can’t recommend it enough!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f87dbbc0bc41" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>