<?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 JS on Medium]]></title>
        <description><![CDATA[Stories by JS on Medium]]></description>
        <link>https://medium.com/@jspeda?source=rss-225180aa2a00------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*HdB6ihv6D6w3-4Jp.</url>
            <title>Stories by JS on Medium</title>
            <link>https://medium.com/@jspeda?source=rss-225180aa2a00------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 18:04:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jspeda/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[A practical guide to fetch(), reduce() and formatting data from an external API]]></title>
            <link>https://medium.com/free-code-camp/a-practical-guide-to-fetch-reduce-and-formatting-data-from-an-external-api-283ddd9bfdcb?source=rss-225180aa2a00------2</link>
            <guid isPermaLink="false">https://medium.com/p/283ddd9bfdcb</guid>
            <category><![CDATA[functional-programming]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[JS]]></dc:creator>
            <pubDate>Mon, 15 May 2017 00:54:04 GMT</pubDate>
            <atom:updated>2017-05-15T00:54:04.515Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nROAmzDLiFCLQ9z7pMx8Wg.jpeg" /><figcaption>Photo credit — Alexander Dummer</figcaption></figure><p>JavaScript has built-in methods that make it easy to get and manipulate data from an external API. I’ll walk through a practical example from one of my current projects that you can use as a template when starting something of your own.</p><p>For this exercise, we will look at current job posting data for New York City agencies. New York City is great about publishing <a href="https://opendata.cityofnewyork.us/">all sorts of datasets</a>, but I chose this particular one because it doesn’t require dealing with API keys — the endpoint is a publicly accessible URL.</p><p>First, we’ll get the data from New York City’s servers by using JavaScript’s Fetch API. It’s is a good way to start working with <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise">promises</a>. I’ll go over the very bare basics here, but I recommend Mariko Kosaka’s excellent illustrated blog <a href="http://kosamari.com/notes/the-promise-of-a-burger-party"><em>The Promise of a Burger Party</em></a> for a more thorough (and delicious) primer.</p><p>If you’ve ever used $.getJSON() in jQuery, you’re mostly there conceptually. Take a look at the code below:</p><pre>const cityJobsData =   fetch(&#39;<a href="https://data.cityofnewyork.us/resource/swhp-yxa4.json&#39;">https://data.cityofnewyork.us/resource/swhp-yxa4.json&#39;</a>);</pre><p>We declare a variable, cityJobsData, and set its value to fetch(the URL that contains the data we want) which returns something called a promise. For now, just think of a promise as the the data we will <em>eventually</em> get back from the URL when the request is complete. We can access and manipulate this data once it loads by subsequently calling then() on cityJobsData. To perform multiple operations, we can keep chaining then() together, making sure we 1) always pass in our data as an argument to the callback, and 2) return a value.</p><pre>const cityJobsData = fetch(&#39;<a href="https://data.cityofnewyork.us/resource/swhp-yxa4.json&#39;">https://data.cityofnewyork.us/resource/swhp-yxa4.json&#39;</a>);</pre><pre>cityJobsData<br>  .then(data =&gt; data.json())</pre><p>In the above snippet, we’re telling the computer to execute everything contained inside then() <em>once the data is retrieved from the URL</em>. This is what we call ‘asynchronous’ code. In this case,.then(data =&gt; data.json()) returns the data in JSON format, which will allow us to operate on it.</p><p>A quick aside for wrangling huge amounts of JSON: If you go in your web browser to the <a href="https://data.cityofnewyork.us/resource/swhp-yxa4.json">URL that contains the data we want</a>, you’ll see an enormous, unformatted block of text that is very hard to read. However, you can copy and paste that text into something like <a href="http://jsonviewer.stack.hu/">jsonviewer.stack.hu</a>. It will show you an organized and hierarchical overview of the contents.</p><p>Let’s say we want to see how many postings there are for each city agency. If we look at our JSON schema in this viewer, we can see that it’s an array of objects. Each object contains all the data that makes up a single job posting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RoXGqr-4JSiGhkfeZvMa0w.png" /><figcaption>screenshot of formatted JSON from jsonviewer.stack.hu</figcaption></figure><p>Note that each object contains a key, agency, whose value is the name of the city agency that has a job available.</p><p>Therefore, if we can somehow keep track of how many times each agency is mentioned throughout this array of objects, we’ll be able to know how many jobs are currently available per agency.</p><p>One way to count the jobs per agency is to use reduce(). <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/Reduce?v=example">From MDN</a>, “The reduce() method applies a function against an accumulator and each element in the array (from left to right) to reduce it to a single value.” If this sounds like a bunch of nonsense to you, don’t worry! It’s more clear with an example.</p><p>Most introductions to reduce() involve simple addition, which is a fine starting point. Let’s walk through this example together:</p><pre>const arr = [1, 2, 4, 6];<br>const added = arr.reduce((accumulator, item) =&gt; {<br> return accumulator + item;<br>}, 0);</pre><pre>console.log(added); // 13</pre><p>Here’s how it works: the reduce() function loops through the array, arr, and adds each item to an accumulator. The accumulator has an initial value of 0 that’s set with reduce()&#39;s second argument, after the callback function. The accumulator’s current value is returned at the end of every loop, which is how the adding happens. Thus, the final value of added is 13.</p><p>If you’re having trouble visualizing this, try adding a console.log() statement before your return that outputs the current values of the accumulator and the item. This way, you’ll be able to see the looping that’s happening behind the scenes. Here’s a set of log statements for the above example:</p><pre>adding 1 to accumulator: 0<br>adding 2 to accumulator: 1<br>adding 4 to accumulator: 3<br>adding 6 to accumulator: 7</pre><p>This is all well and good, and it’s fun to do some addition with *~`*functional programming*`~*, but did you know reduce() can do more than simply count things? And that the accumulator can be something other than a number?</p><p>You can do all sorts of cool stuff with reduce() — it’s like a Swiss Army Knife. In our case, we’ll use it to find out how many current job postings there are per New York City agency. This might seem like a big leap from simply adding numbers together, but the core concepts of looping and accumulating are the same.</p><p>This time, instead of reducing an array of four numbers, we want to reduce our JSON blob of job posting data. And instead of reducing to a single number, we’re going to reduce to a single <em>object</em>. Yes, an object! Once the function is completed, the accumulator object’s keys will be the names of the city agencies and the keys’ values will be the number of postings they have, like this: {&quot;name of agency&quot;: number of job postings}. Here’s the whole program:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b1e72921523f47377e20a382c3f7079f/href">https://medium.com/media/b1e72921523f47377e20a382c3f7079f/href</a></iframe><p>How does this work, exactly? Let’s break it down. Each time around the loop, we’re looking at a specific value, i.e., one object in data, our aforementioned array of objects. We’re checking to see if a key with the name of the current agency (value.agency) already exists within our accumulator object. If not, we add it to the accumulator object and set its value to 1. If a key with the name of the current agency <em>already exists within the accumulator object</em>, we add 1 to its existing value. We return the accumulator object when we’re done and get this nice set of data:</p><pre>{ &#39;FIRE DEPARTMENT&#39;: 17,<br>  &#39;DEPT OF ENVIRONMENT PROTECTION&#39;: 134,<br>  &#39;DEPARTMENT OF INVESTIGATION&#39;: 22,<br>  &#39;DEPARTMENT OF SANITATION&#39;: 14,<br>  &#39;DEPT OF HEALTH/MENTAL HYGIENE&#39;: 247,<br>  &#39;OFFICE OF THE COMPTROLLER&#39;: 14,<br>  &#39;ADMIN FOR CHILDREN\&#39;S SVCS&#39;: 43,<br>  &#39;DEPT OF DESIGN &amp; CONSTRUCTION&#39;: 48,<br>  &#39;ADMIN TRIALS AND HEARINGS&#39;: 16,<br>  &#39;DEPT OF PARKS &amp; RECREATION&#39;: 34,<br>  &#39;HUMAN RIGHTS COMMISSION&#39;: 4,<br>  &#39;POLICE DEPARTMENT&#39;: 36,<br>  &#39;DEPT OF INFO TECH &amp; TELECOMM&#39;: 50,<br>  &#39;DISTRICT ATTORNEY KINGS COUNTY&#39;: 4,<br>  &#39;TAXI &amp; LIMOUSINE COMMISSION&#39;: 11,<br>  &#39;HOUSING PRESERVATION &amp; DVLPMNT&#39;: 21,<br>  &#39;DEPARTMENT OF BUSINESS SERV.&#39;: 18,<br>  &#39;HRA/DEPT OF SOCIAL SERVICES&#39;: 31,<br>  &#39;DEPARTMENT OF PROBATION&#39;: 3,<br>  &#39;TAX COMMISSION&#39;: 4,<br>  &#39;NYC EMPLOYEES RETIREMENT SYS&#39;: 6,<br>  &#39;OFFICE OF COLLECTIVE BARGAININ&#39;: 2,<br>  &#39;DEPARTMENT OF BUILDINGS&#39;: 9,<br>  &#39;DEPARTMENT OF FINANCE&#39;: 29,<br>  &#39;LAW DEPARTMENT&#39;: 21,<br>  &#39;DEPARTMENT OF CORRECTION&#39;: 12,<br>  &#39;DEPARTMENT OF TRANSPORTATION&#39;: 67,<br>  &#39;DEPT OF YOUTH &amp; COMM DEV SRVS&#39;: 5,<br>  &#39;FINANCIAL INFO SVCS AGENCY&#39;: 7,<br>  &#39;CULTURAL AFFAIRS&#39;: 1,<br>  &#39;OFFICE OF EMERGENCY MANAGEMENT&#39;: 12,<br>  &#39;DEPARTMENT OF CITY PLANNING&#39;: 5,<br>  &#39;DEPT OF CITYWIDE ADMIN SVCS&#39;: 15,<br>  &#39;DEPT. OF HOMELESS SERVICES&#39;: 3,<br>  &#39;DEPARTMENT FOR THE AGING&#39;: 2,<br>  &#39;CONSUMER AFFAIRS&#39;: 7,<br>  &#39;MAYORS OFFICE OF CONTRACT SVCS&#39;: 7,<br>  &#39;DISTRICT ATTORNEY RICHMOND COU&#39;: 3,<br>  &#39;NYC HOUSING AUTHORITY&#39;: 9,<br>  &#39;CIVILIAN COMPLAINT REVIEW BD&#39;: 5,<br>  &#39;OFF OF PAYROLL ADMINISTRATION&#39;: 1,<br>  &#39;EQUAL EMPLOY PRACTICES COMM&#39;: 1 }</pre><p><em>Et Voila</em>! We now know that if we want to work for New York City’s government, we should check out the Department of Health and Mental Hygiene’s 247 openings!</p><p>We can do a bunch of useful things with this data — personally, I want to dip my toes into data visualization, so I’ll be using it to make a simple chart. I hope you’ll be able to use this example as a jumping-off point for your own projects.</p><p>If you enjoyed this article, please reach out to me on <a href="http://twitter.com/j_speda">Twitter</a>!</p><p>Thanks to <a href="http://twitter.com/jimcodes">Jim O’Brien</a> for editing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=283ddd9bfdcb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/free-code-camp/a-practical-guide-to-fetch-reduce-and-formatting-data-from-an-external-api-283ddd9bfdcb">A practical guide to fetch(), reduce() and formatting data from an external API</a> was originally published in <a href="https://medium.com/free-code-camp">We’ve moved to freeCodeCamp.org/news</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[(Not quite) 100 Days of Code — A Postmortem]]></title>
            <link>https://medium.com/free-code-camp/not-quite-100-days-of-code-a-postmortem-d27124f023f2?source=rss-225180aa2a00------2</link>
            <guid isPermaLink="false">https://medium.com/p/d27124f023f2</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[habit-building]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[JS]]></dc:creator>
            <pubDate>Sat, 22 Apr 2017 14:05:47 GMT</pubDate>
            <atom:updated>2017-05-17T18:02:26.273Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OVHrWU4rKjMbV7lQBjNV1Q.jpeg" /><figcaption>image credit — Eric Rothermel</figcaption></figure><p>At the end of last year, I wrote about my experience coding and making daily commits to GitHub for 30 consecutive days. I also pledged to keep the streak going for as long as I could. I am happy to report that I made it through 90 straight days! It was an incredible experience, and I learned a ton.</p><p>The following is an overview of the projects I completed and some lessons I learned along the way. I hope it motivates some of you to make your own daily commitment to code.</p><h3><strong>Completed freeCodeCamp’s Front-End Certification</strong></h3><p>I had worked on the more basic freeCodeCamp material ages ago. I still had to complete eight intermediate and advanced front-end projects and a series of small coding challenges before I could claim my certification.</p><p>The projects covered a wide variety of topics and proved quite challenging at times. I used an API to display the local weather, and for another I built a working clone of the children’s game Simon. The combination of good resources and the patience of some more experienced friends helped me finish them to earn my certification.</p><p>These projects taught me how to organize and write clean code. I honed my JavaScript skills and learned how the language differs from other more classically object-oriented languages such as Ruby and Python.</p><p>A few weeks after I earned my certification, I went back and refactored some of the initial projects. I applied the <a href="https://en.wikipedia.org/wiki/Don%27t_repeat_yourself">DRY</a> principle and included some functional programming concepts I had subsequently learned. It was great fun trying to eliminate all of the for loops in my code.</p><h3><strong>Wrote a widely-shared (for me, anyway) article about learning JavaScript</strong></h3><p>After finishing my first blog, which freeCodeCamp was kind enough to publish on its Medium page, I had the itch to write something else.</p><p>Because it can be so hard to figure out which learning resources are actually worthwhile, I decided to put together a <a href="https://medium.freecodecamp.com/a-beginners-javascript-study-plan-27f1d698ea5e">study plan for beginners looking to learn JavaScript</a> based on what I had found useful. The article was again published by freeCodeCamp and currently has over 15 thousand views and 700 recommends.</p><p>Not exactly ‘viral,’ sure, but for someone who had never done <em>any</em> public writing as recently as six months ago, it was exhilarating to see my article resonate with a bunch of people.</p><h3>Learned React</h3><p>In addition to completing the freeCodeCamp Front-End Certification, I also began learning React. Thanks to a few great tutorials (shout out to the excellent Wes Bos course, <a href="https://reactforbeginners.com/">React for Beginners</a>), I was able to finish a few React projects. These included a live-searchable recipe repository. I also became comfortable using the <a href="https://github.com/facebookincubator/create-react-app">create-react-app CLI</a> tool to scaffold React applications.</p><h3>Broke my streak on Day 91</h3><p>With progress so great, why did I stop? The path I paved for myself had slowed down. I felt intimidated by some of the upcoming projects on freeCodeCamp, so I shifted my efforts to learning D3.js, a data-visualization library. At the time, it proved to be a bit too impenetrable for me despite multiple attempts to grasp it.</p><p>Also, I didn’t have a compelling personal project to work on, and needed a break from the grind of working full-time and coding at night for multiple hours.</p><p>The most important thing I learned about keeping a streak like this going is to <em>always know what to work on tomorrow</em>. When you sit down at your computer, you should already have a clear idea of what you’re going to do. If you make that decision ahead of time, it removes a barrier to getting started.</p><p>Take a moment before you decide to stop coding for the day and make sure you have something concrete to do tomorrow. I stuck to this plan for the vast majority of my streak and it was a major factor in my success. It was only when I stopped planning ahead that I eventually missed a day.</p><h3>A completely worthwhile experience</h3><p>At the beginning of my not-quite #100DaysOfCode, I had some familiarity with the Ruby on Rails ecosystem and HTML/CSS with only a few hours of JavaScript under my belt.</p><p>Three months later, I gained a good, foundational knowledge of JavaScript, learned React, got a bunch of cool projects in my GitHub portfolio, and had two articles published on freeCodeCamp’s Medium page. I am a far better developer today than I was when I started this daily coding experiment a few months ago.</p><h3>Next steps</h3><p>Having taken a pretty substantial break, I want to continue working on React projects, dip my toes into some backend JavaScript, and learn more about algorithms and data structures. I also hope to keep writing.</p><p>If you enjoyed this article and want to continue the discussion, come find me on <a href="http://www.twitter.com/j_speda">Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d27124f023f2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/free-code-camp/not-quite-100-days-of-code-a-postmortem-d27124f023f2">(Not quite) 100 Days of Code — A Postmortem</a> was originally published in <a href="https://medium.com/free-code-camp">We’ve moved to freeCodeCamp.org/news</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Beginner’s JavaScript Study Plan]]></title>
            <link>https://medium.com/free-code-camp/a-beginners-javascript-study-plan-27f1d698ea5e?source=rss-225180aa2a00------2</link>
            <guid isPermaLink="false">https://medium.com/p/27f1d698ea5e</guid>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[JS]]></dc:creator>
            <pubDate>Wed, 18 Jan 2017 18:22:54 GMT</pubDate>
            <atom:updated>2017-01-25T03:30:41.063Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uwXvMVTx3L2TcZsLDU4dwg.jpeg" /></figure><p>So you want to learn JavaScript? Congratulations! In 2017, there are more resources available than ever before, in a wide variety of formats for you to get started.</p><p>While there has truly never been a better time in history to learn a new skill, It’s also never been more confusing if you’re trying to figure out the best way to do so, given the huge amount of available options and the wild variations in quality between these materials. If you’ve ever been recommended <em>Eloquent JavaScript </em>during<em> </em>the early stages of your coding journey, you know what I’m talking about.</p><p>I hope to illuminate a path in this article for a beginner to follow that will start them on the road toward JavaScript competency. It’s a path that I’ve been personally following and have found success with, having recently completed freeCodeCamp’s front-end certificate.</p><p>Be sure to drop me a line in 3 months when you’ve sorted everything out and decided on the best course of action (or moved on to something more fruitful).</p><h3>Step 1: freeCodeCamp’s JavaScript section</h3><p><a href="https://freecodecamp.com/">freeCodeCamp</a> is an incredible resource for learning the basics (and beyond) of web development.</p><p>From this point on, I will assume familiarity with HTML and CSS, but if you’re totally new to programming, freeCodeCamp has you covered there, too.</p><p>Using a friendly, in-browser text-editor, freeCodeCamp will first give you a small taste of the popular JavaScript library, jQuery, and then dive right in to pure JavaScript syntax, and how to perform various tasks such as boolean operations, string and array manipulation, loops, and more.</p><h4>Step 1.5: Reinforcement with Codecademy’s JavaScript track.</h4><p>If you’re anything like me, you’ll need some reinforcement. Not everything is going to sink in on the first go-around.</p><p>One option is to just re-do the freeCodeCamp exercises, but I prefer using multiple resources to keep things fresh and interesting. It can also be valuable to get someone else’s perspective on the same topic. Codecademy is great for this. You’ll experience many of the same areas and issues from a slightly different angle.</p><h3>Step 2: Tony Alicea’s JavaScript: Understanding The Weird Parts</h3><p>Once you’ve completed everything up through through freeCodeCamp’s Object Oriented and Functional Programming modules, and the Codecademy JavaScript track, you’ll hopefully be ready for something a little more in-depth.</p><p><a href="http://learnwebdev.net/"><em>JavaScript: Understanding the Weird Parts</em></a> is an excellent premium video series that goes deep into the workings of the language in a very accessible and understandable way. The 11.5-hour series is jam-packed with practical information that you’ll be able to put to use in your programs.</p><p>You’ll learn about scope, closures, prototypal inheritance, first-class functions, and more in this comprehensive series. It’s well-worth the $20.</p><p>As with any book or video course, be sure to code along and take your own notes for later reference.</p><p>As you work through this series, continue to plug away at freeCodeCamp’s challenges and start their intermediate front-end projects. These projects are unguided, which may sound scary, but I guarantee you will learn a ton by doing them. They will force you to confront the gaps in your knowledge and will rapidly increase your Googling skills for when you get stuck and don’t know how to implement a certain feature.</p><h3>Step 3: Kyle Simpson’s You Don’t Know JS</h3><p>I’m not sure what I can say about this series that hasn’t been said elsewhere at this point, but it’s incredible. Once you finish Tony Alicea’s course, start reading <em>You Don’t Know JS</em> while you continue to work on the freeCodeCamp curriculum and projects. Simpson is more than deserving of your money, but if you can’t afford to pay, the books are all freely available <a href="https://github.com/getify/You-Dont-Know-JS">on his GitHub</a>.</p><p>You should at least read the <em>Scope &amp; Closures</em> and <em>This &amp; Object</em> Prototypes volumes. These books will reinforce what you learned from Tony Alicea and also contradict and challenge that material at times. This is good! Kyle Simpson is an opinionated guy, and it’s super valuable to get his expert perspective on things, like the usefulness of the object oriented programming paradigm in a language like JavaScript. Even if some of the issues feel beyond your grasp, there’s value in simply being aware of them.</p><p>This series will make you a better developer while also inform your perspective on the various ideological conflicts currently happening in the JavaScript community.</p><h3>Some notes about struggling, not knowing the answers, and perseverance.</h3><p>There will be many times when you hit a wall — when you don’t know the answer to some problem and feel like you’ll never figure it out. I’d like to share just a few techniques for when this happens.</p><h4>1. Walk away</h4><p>Take a break. Step away from the computer. Get some tea or coffee. Think about something else for a little while. It can be valuable to just clear your head for a little while. You’ll be surprised how many times you’ll be able to quickly solve the problem when you return.</p><h4>2. Ask for help</h4><p>Don’t be embarrassed or ashamed to ask for help. Sometimes a nudge in the right direction is all you need to get back on track. In my experience, people love helping out others, and are more than happy to spend a few minutes on your problem. The <a href="https://www.google.com/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=1&amp;cad=rja&amp;uact=8&amp;ved=0ahUKEwjthY_M6cvRAhUPfiYKHTqAAMQQFggbMAA&amp;url=https%3A%2F%2Fgitter.im%2Ffreecodecamp%2Ffreecodecamp&amp;usg=AFQjCNFfb6q1G6N2Ey3sX2DIbLk6CY4LxA&amp;sig2=AhiYRwdihtqToCnjhhGkPw&amp;bvm=bv.144224172,d.eWE">freeCodeCamp community on Gitter</a> and the <a href="https://codenewbie.typeform.com/to/uwsWlZ">CodeNewbie Slack channel</a> are great for this.</p><h4>3. Move on to something else</h4><p>If you really can’t get it, there’s no harm in moving on to another topic. It’s nice to have a couple projects that you can bounce between when you are feeling stuck on one or the other.</p><h3>This is just a guide</h3><p>Learning is highly personal. All the resources I mentioned above have been extremely helpful to me on my journey to become a self-sufficient JavaScript developer.</p><p>I wrote this out of the frustration I experienced when trying to choose between the million-and a half educational resources out there. It was nice to find a plan that finally worked for me after receiving some well-meaning, but misguided advice (“<em>Eloquent JavaScript</em> is a great book for beginners!”), and tons of starts and stops.</p><p>While I’m nowhere near a JavaScript expert, I hope to provide perspective from someone who still remembers what it’s like to be a total beginner. So much instructional material is (rightfully) written by masters of their craft. But many of those masters have forgotten the experience of being a lowly beginner, and expect newcomers to make preposterous connections and leaps in logic. This is why so much instructional material can be wholly unhelpful.</p><h3>Quincy Larson on Twitter</h3><p>Every coding tutorial ever written</p><p>If this plan helps you, inspires you to get started, or even has you fuming in disagreement, I’d love to hear from you <a href="https://twitter.com/j_speda">on Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27f1d698ea5e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/free-code-camp/a-beginners-javascript-study-plan-27f1d698ea5e">A Beginner’s JavaScript Study Plan</a> was originally published in <a href="https://medium.com/free-code-camp">We’ve moved to freeCodeCamp.org/news</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lessons from my month-long GitHub commit streak]]></title>
            <link>https://medium.com/free-code-camp/lessons-from-my-month-long-github-commit-streak-b8f3167d34ac?source=rss-225180aa2a00------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8f3167d34ac</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[freecodecamp]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[JS]]></dc:creator>
            <pubDate>Tue, 27 Dec 2016 03:34:27 GMT</pubDate>
            <atom:updated>2017-01-26T01:28:01.465Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rOsLmv15-FG_g0InyWLfuQ.png" /></figure><blockquote>“I want to learn JavaScript. Like, really learn it. Like, truly <em>understand it.</em>” — me in November 2016</blockquote><p>A lofty goal, for sure. Especially for someone who’s only been programming for about six months, decidedly in <em>not-JavaScript </em>(Ruby, if you must know)<em>. </em>A particularly daunting task<em> </em>after you’ve been told over and over again how <em>weird</em> JavaScript is. But I can be stubborn.</p><p>About two months ago, I wrapped up a stint at <a href="https://thefirehoseproject.com/">The Firehose Project</a>, where I studied part-time while holding down a day job as an attorney. It was a great experience. I learned about building complex Ruby on Rails applications, test-driven development, and more. But once the program ended, I wanted to learn more about JavaScript — the language powering so much of the web.</p><p>I turned to <a href="https://freecodecamp.com/">freeCodeCamp</a>, the resource I initially used to learn basic HTML and CSS before enrolling in The Firehose Project. freeCodeCamp has a robust, project-driven, JavaScript-oriented curriculum that seemed like the perfect option to master the basics.</p><p>Without the structure of a paid program, however, I feared that I would fall victim to procrastination or otherwise come up with some excuse as to why I should stop when things got hard.</p><p>I came up with a solution: work through the freeCodeCamp projects and make at least one commit to GitHub every single day for at least one month. No matter what. No matter whether I felt like coding. No matter how I was feeling on any particular day. And I’m happy to say I accomplished my goal. And what I learned surprised me.</p><h4>Lesson one: even on days when I didn’t feel like coding, I often happily worked for hours once I forced myself to get started.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/113/1*0yrq77XOiYmSdXNsYsZVAw.png" /><figcaption>30 days (and counting) of commits!</figcaption></figure><blockquote>“The pleasures of not writing are so great that if you ever start indulging them you will never write again” — John Updike.</blockquote><p>It’s an awful idea to just sit around waiting for the right moment or inspiration to strike. While this idea of waiting for one’s muse mostly comes up in creative fields, a variation of it can take hold in other disciplines.</p><p>Don’t wait until you’re “in the mood to code” or until you’ve thought of a great idea for a new app. Don’t wait for inspiration. Just start.</p><p>If you don’t have any active projects, log on to <a href="https://codewars.com/">Code Wars</a> and do a few kata. Make a simple implementation in that framework you’ve been meaning to check out. This field is vast enough that there is always <em>something</em> you could be working on.</p><p>Besides, the simple act of starting might inspire you to continue.</p><p>During the last month, there were more than a couple days where, after a long day at work, the last thing I wanted to do was sit down at my desk at home and struggle with some coding problem. But more often than not, once I started working, I found it easy to keep going.</p><p>The mind has a terrible way of making mountains out of molehills. Don’t fall for it.</p><h4>Lesson two: I learned that I was able to commit to something for a period of time — not because I was paying a lot of money for it, or because I was required — but because I set a goal that I wanted to achieve.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*11DcHbXxatsSrL04lgU6DQ.jpeg" /><figcaption>Don’t let Shia down.</figcaption></figure><p>I have trouble staying committed to things I don’t actively find fascinating.</p><p>There’s a brief honeymoon phase with every new hobby I pick up where it’s the only thing I can think about during the day. This lasts for about a month and it goes something like this: I’m progressing at a rapid pace, learning something awesome every day. I’m feeling more confident. I start have delusions of grandeur. “I will be a master [pianist / photographer/ artist / songwriter] soon,” I whisper to myself.</p><p>And then, all of a sudden, I stop noticeably improving. It gets hard. I hit a wall. The magic goes away. I wonder if maybe this thing isn’t for me after all.</p><p>Unless you’re a prodigy, you’ve probably experienced something similar. It’s so easy to quit (as anyone who ever briefly saw me with a DSLR around my neck or a sketchbook in my hands can testify). But this is a terrible way to ever get good at anything.</p><p>Learning to program is not easy. And anyone can tell you it’s certainly not always fun. There have been times when I have wanted to give up because I felt I wasn’t progressing quickly enough. But learning to program is more akin to a marathon than a sprint, and it’s important to keep this in mind when you think about your goals, and where you want to be in a few weeks, or a month, or a year. Nobody becomes an expert in this stuff overnight.</p><p>With that in mind, it’s really important to just gut it out and persevere through the tough times.</p><p>I have long thought my tendency to stop doing stuff when it got boring or difficult was just a personal defect. Something I was bound to live with for the rest of my life. Me, the guy who likes to dabble in everything but is not actually good at any one thing.</p><p>It’s true that there’s never been a better time to learn a new skill or hobby — there are so many free resources, and the barrier of entry is often so low, that there’s basically no limit to what you can learn. It’s really incredible and I wouldn’t have it any other way.</p><p>But it’s also not so great if you’re like me and have a wandering eye when it comes to interests and hobbies. In 2016, it’s incredibly easy to jump from topic to topic when the going gets tough or the spark fades. If you want to get good (at anything), it’s important to resist this temptation, however strong.</p><p>Coding and pushing daily commits to GitHub for a month-straight helped me realize that I have the power to stick it out through the tough times and keep going, even when it’s not fun or exciting.</p><h4>Lesson three: consistent practice is the best kind of practice.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*SEj5y_Ny-Gecd64Iy_p__g.jpeg" /><figcaption>🔑</figcaption></figure><p>Consistent practice of a moderate or even short length is better than having a couple marathon sessions once or twice a week. There are tons of studies on practice and training that confirm this, but you will see the evidence for yourself if you take this challenge.</p><p>With consistent practice, you have the opportunity to reinforce what you learned in days prior, before you forget everything. This reinforcement is key to understanding tough programming concepts. It’s not enough to sit down for a few hours, read about how this or prototypal inheritance work and then walk away for a week. If you haven’t completely forgotten what you read by then, well, congratulations on having a better memory than me.</p><p>The far better tactic is to read, take notes, practice some implementations, and then <em>go back the next day and review what you’ve done</em>. By practicing consistently, and structuring your sessions so you are in a cycle of constantly reviewing old material while also learning new material, you ensure progression while solidifying a foundation of knowledge.</p><h4>Lesson four: keeping a journal helped me stay motivated.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/417/1*JZtEmzVSXKgXEraSrQRNNw.jpeg" /><figcaption>“Dear Journal…”</figcaption></figure><p>Seeing all those green boxes on my GitHub profile is awesome, but I chose to also keep a journal of sorts so I could look back on my accomplishments in detail. My journal also allowed me to keep track of all my non-GitHub work, of which there was plenty (because, like I said earlier, once I got started I often did not want to stop).</p><p>Your journal can be anything — a Google Doc, a blank notebook, or a notes app on your phone. I chose to go with a small, daily planner that has a calendar laid out for each month and then on subsequent pages, space for writing about each day. At the end of every night, I would check off the day in the calendar section and then write some notes about what I did that day. Let me tell you, it feels incredible to check those boxes.</p><p>Whenever you’re feeling discouraged or down, you can look back into your journal and see how far you’ve come. I was really surprised at how empowering this turned out to be.</p><h4>What’s next? Join me!</h4><p>Looking ahead to the new year, I want to keep this streak going as long as possible. While I’m nowhere near where I want to be in terms of skill-level, I’ve already learned so much in the past month, and I am completely sold on this admittedly not-so-revolutionary method (shout out to <a href="https://medium.freecodecamp.com/join-the-100daysofcode-556ddb4579e4#.h37k9z229">#100DaysOfCode</a>, a slightly more structured and significantly longer version of my personal challenge to myself).</p><p>I don’t see why it wouldn’t work for anyone, at any skill, in any topic.</p><p>If you feel inspired to start your own #CommitMonth, hit me up <a href="https://twitter.com/j_speda">on twitter</a>. I’d love to hear from you.</p><blockquote>“Amateurs sit and wait for inspiration, the rest of us just get up and go to work.” — Stephen King</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8f3167d34ac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/free-code-camp/lessons-from-my-month-long-github-commit-streak-b8f3167d34ac">Lessons from my month-long GitHub commit streak</a> was originally published in <a href="https://medium.com/free-code-camp">We’ve moved to freeCodeCamp.org/news</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>