<?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 Julius Zerwick on Medium]]></title>
        <description><![CDATA[Stories by Julius Zerwick on Medium]]></description>
        <link>https://medium.com/@juliuszerwick?source=rss-54c5cb7f84d8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*QCwqR0IFlrHeJL8CqmTCXg.jpeg</url>
            <title>Stories by Julius Zerwick on Medium</title>
            <link>https://medium.com/@juliuszerwick?source=rss-54c5cb7f84d8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 01:59:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@juliuszerwick/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[How I navigated the job hunt and landed my dream job]]></title>
            <link>https://medium.com/free-code-camp/how-i-navigated-the-job-hunt-and-landed-my-dream-job-b37bf3d0d630?source=rss-54c5cb7f84d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b37bf3d0d630</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Julius Zerwick]]></dc:creator>
            <pubDate>Fri, 05 Apr 2019 16:25:54 GMT</pubDate>
            <atom:updated>2019-05-22T13:25:46.892Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*97LZJyxxYi4gf4A6EbIdlQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/kheTI8pIywU?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Emiliano Bar</a> on <a href="https://unsplash.com/search/photos/new-york-city?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>This article is about how I went through my job hunt for a full time position as a software engineer in New York City and ended up with my dream job. I had spent two years building my skills and had aspirations to work at a top tech company with a high bar for engineering excellence.</p><p>I knew this goal would not be easy to achieve, especially without a CS degree, barely having any network in New York City, and having to compete against engineers from top schools. It would be a long shot, and I was prepared for the long haul.</p><p><strong>9 weeks later…</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fl4JySAWfMaY7w88sU%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fl4JySAWfMaY7w88sU%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia2.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExNGtsNWplamozeGJ1czliNGdvbWw2NDI1MGVnZXpoNG05ZWhyOTdreCZlcD12MV9naWZzX2dpZklkJmN0PWc%2Fl4JySAWfMaY7w88sU%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="246" frameborder="0" scrolling="no"><a href="https://medium.com/media/6f715a6805bb2dacd5df0e22da58318f/href">https://medium.com/media/6f715a6805bb2dacd5df0e22da58318f/href</a></iframe><p>I’m ecstatic to say that I’ve accepted an offer from DigitalOcean to work as a Software Engineer II from their NYC HQ!</p><p>This success came after countless study sessions, mock interviews, hours of practice, and facing numerous challenges &amp; rejections. But I kept my spirits up and came out the other end happier than I imagined possible.</p><p><strong>How did you go from start to finish?</strong></p><p>That question is what this article is all about! I’ll be detailing my preparation process for interviews, how I built my network, and managed myself during this job hunt.</p><p>That being said, everyone’s experiences are different and should pull from this article what they feel will benefit them. No two job hunts are the same and there are different factors in each one.</p><p>With that said, let’s dive in!</p><h3><strong>First things first: build a solid foundation</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bkJzT9fx13c_oOfUbHIb6g.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/vII7qKAk-9A?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">NESA by Makers</a> on <a href="https://unsplash.com/search/photos/software-development?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Before anything else, it’s vital that you have a rock solid foundation in the fundamentals of software engineering. Instead of chasing after the hottest technologies, what’s important is to have the technical foundation needed to learn new things quickly and deeply.</p><p>In my opinion, the best way to do this is to pick one industry-proven language and stick with it while learning about variables, functions, tools, software design, databases, APIs, and building web applications. This allowed me focus on depth in my knowledge, proficiency in solving coding challenges, and experience in building quality projects.</p><p>To build my fundamentals, I chose to study at <a href="https://launchschool.com/">Launch School</a> which offers an extensive curriculum and rigorous assessment process that ensured that I had deeply learned the fundamentals before progressing.</p><h3>Build a project that impresses employers &amp; engineers</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PodXWdegqPnOmtgZDT94kQ.gif" /><figcaption>SpaceCraft demo</figcaption></figure><p>In the current day, there are multitudes of bootcamps and online tutorials that provide aspiring software developers with projects to help them land a job.</p><p>However, there is now a saturation in the market of developers with simple CRUD apps or clones of popular apps like Instagram, Netflix, Reddit, etc. These projects no longer impress employers or other engineers as they once did.</p><p>That said, many engineers need some way to evaluate you before giving you a referral and there is no replacement for showing your skills off with a solid project.</p><p>That’s why <a href="https://gooi.tech/">Gooi</a>, <a href="https://njohnson7.github.io/">Nick</a>, and I built <a href="https://spacecraft-repl.com/">SpaceCraft</a>, a real-time collaborative REPL that allows developers to write and execute code in the browser for Ruby, JavaScript, and Python.</p><p>It was an incredible experience, and also a TON of work. You can read more about how we built SpaceCraft in this <a href="https://hackernoon.com/building-spacecraft-a-real-time-collaborative-repl-deebcf084ed9">article</a> or read our <a href="https://spacecraft-repl.com/whitepaper">case study</a>.</p><p>We spent hundreds of hours researching how to build a REPL, enable real-time collaboration, use Docker to create isolated user sessions, and handle user requests with a proxy server.</p><h3>Market yourself effectively</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Flivestream.com%2Faccounts%2F686369%2Fevents%2F8535115%2Fvideos%2F186248334%2Fplayer%3Fwidth%3D640%26height%3D360%26autoPlay%3Dtrue%26mute%3Dfalse&amp;url=https%3A%2F%2Flivestream.com%2Finternetsociety%2Fjs-nyc-jan19%2Fvideos%2F186248334&amp;image=https%3A%2F%2Fimg.new.livestream.com%2Fevents%2F0000000000823c4b%2F4cc27cb7-379a-4413-99c1-1ece3a4be0e7_270_150x83.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=livestream" width="640" height="360" frameborder="0" scrolling="no"><a href="https://medium.com/media/6caa6cbadb228f40bd5697c72bc7aad1/href">https://medium.com/media/6caa6cbadb228f40bd5697c72bc7aad1/href</a></iframe><p>While SpaceCraft may showcase our skills, I still needed to get people to look at it. Since I had relocated to NYC for my job hunt, my professional network was close to nil and I did my best to put myself in front of as many engineers as possible.</p><p>That’s why our team wrote our case study, an article on HackerNoon, and presented at Meetups. These efforts helped us stand out among the sea of other applicants and generated interest from employers &amp; engineers.</p><p>Presenting at Meetups were a game changer for me as they got my name out there and procured referrals to several companies, along with giving me the chance to practice and refine my communication skills.</p><p>I also built a <a href="https://rouxcaesar.github.io/">personal website</a> and beefed up my <a href="https://www.linkedin.com/in/julius-zerwick-842000b2/">LinkedIn</a> &amp; <a href="https://angel.co/julius-zerwick?al_content=view+your+profile&amp;al_source=transaction_feed%2Fnetwork_sidebar">AngelList</a> profiles in order to make it easier for prospective companies to find me and see my work.</p><p>Devoting time to market yourself and skill set through writing articles, presenting at events, and professional networking sites can lead to a big payoff in the interview process.</p><p>I had a big increase in the number of engineers and companies reaching out to me after seeing my updated profiles and hearing me present, and having a video of my presentation to include in my outreach emails resulted in a higher response rate and more interviews.</p><h3>Reach out to engineers &amp; companies</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FmW05nwEyXLP0Y%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FmW05nwEyXLP0Y%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FmW05nwEyXLP0Y%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="243" frameborder="0" scrolling="no"><a href="https://medium.com/media/f6c4f871f7e64b617b594fa8f1cb2a68/href">https://medium.com/media/f6c4f871f7e64b617b594fa8f1cb2a68/href</a></iframe><p>In the same vein, I made sure to consistently reach out to engineers at companies I was interested in. Using LinkedIn Connect requests, I had over a dozen coffee meetings with engineers from DigitalOcean, Cockroach Labs, Oscar Health, DataDog, Peloton, and more. These meetings helped me get a feel for the job market in NYC, hear an insider perspective on company culture and teams, and gain referrals.</p><p>My advice is to approach these meetings casually and with interest in your fellow engineer’s work, career, and company. Don’t go in asking for a referral at the beginning, many times they will offer to refer you if you’re nice and the conversation goes well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*hhoIR1BlNh0uYDiXSFEQpg.gif" /></figure><p>Another form of outreach that I did was more directly emailing engineers. Whenever I found a job posting that I really liked, I would reach out to an engineer who works at the company through LinkedIn Inmail, using <a href="https://chrome.google.com/webstore/detail/clearbit-connect-supercha/pmnhcgfcafcnkbengdcanjablaabjplo?hl=en">Clearbit Connect</a> when needed to find contact info.</p><p>In the email, I would include an introduction on my background, my most impressive project, a link to one of my presentations, and ask if they were open to chatting about the position.</p><p>This form of outreach lead to my highest response rate out of any other avenue with nearly 1/3 of all my emails getting a response. Remember, the job hunt is entirely a numbers game and it’s best to try out all forms of outreach to see which nets you the highest returns.</p><h3>Study, practice, repeat</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JU7-Ksjiq4PaSbnS1-A6gw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/3V8xo5Gbusk?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Kaleidico</a> on <a href="https://unsplash.com/search/photos/whiteboard?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>That said, none of these efforts would go anywhere if I didn’t have the skills to succeed in the technical interviews. With a solid foundation in the fundamentals, I needed to spend my time solving coding challenges and studying topic relevant to the positions.</p><p>The types of questions and challenges you can face in interviews are VAST and often times you won’t know what to expect. Many of the top companies will focus on algorithms and data structures, while startups and mid-size companies may focus on more “practical” problems like refactoring an existing class or adding features to a basic project.</p><p>My advice is to study a variety of coding challenges and do your best to predict the questions they will ask you. For algorithms and data structures, my main resources for building a foundation and conceptual understanding were:</p><ul><li><a href="https://www.amazon.com/Common-Sense-Guide-Data-Structures-Algorithms/dp/1680502441">A Common-Sense Guide to Data Structures and Algorithms</a></li><li><a href="https://www.amazon.com/Cracking-Coding-Interview-Programming-Questions/dp/0984782850/ref=sr_1_1?crid=3B576YLQLTSY8&amp;keywords=cracking+the+coding+interview&amp;qid=1553352055&amp;s=gateway&amp;sprefix=cracking%2Caps%2C285&amp;sr=8-1">Cracking the Coding Interview</a></li><li><a href="https://medium.com/basecs">BaseCS</a></li></ul><p>I also solved 2–3 problems a day on <a href="https://leetcode.com/">LeetCode</a> for 5–6 days a week.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/470/1*t_azHzMuCidoyf_ItbhIhA.gif" /></figure><p>Many companies will also have a system design interview to assess what level to hire you for. If you’re aiming for mid-to-senior level roles, you’ll need to devote more time to this area.</p><p>I found the best resources to be <a href="https://www.educative.io/collection/5668639101419520/5649050225344512?authorName=Design%20Gurus">Grokking the System Design Interview</a> and reading various blogs on specific topics. Here are a few blogs I’d recommend:</p><ul><li><a href="https://www.allthingsdistributed.com/2018/06/purpose-built-databases-in-aws.html">All Things Distributed</a></li><li><a href="http://highscalability.com/">High Scalability</a></li><li><a href="http://blog.gainlo.co/index.php/2017/03/24/chapter-5-system-design-interviews-part-complete-guide-google-interview-preparation/">Gainlo</a></li><li><a href="https://medium.com/baseds">BaseDS</a></li></ul><p>Another very common step is to complete a take home challenge. The variety of these challenges can make it hard to prepare for, but there are some common topics. Several that I saw were:</p><ul><li>Build a RESTful API that handles several provided cURL requests</li><li>Build a CLI app that stores inputs (like albums, artists, and release year) and allows users to retrieve them</li><li>Build a game using React/Rails (ex: Tic-Tac-Toe, Blackjack, Minesweeper)</li><li>Given a spec and example of the finished product, create a web page that is as close to pixel perfect to the example as possible.</li></ul><p>The upside is that you have more time to complete them in the comfort of your own home, and there are lots of opportunities to impress by writing a comprehensive test suite, identifying &amp; addressing edge cases, and finding extra touches to add.</p><p>Over my job hunt, I typically spent Monday-Thursday applying to companies, doing outreach, and solving LeetCode challenges or studying system design. I reserved Friday-Saturday to practice building a take home project. Here are some to consider:</p><ul><li><a href="https://x-team.com/blog/how-to-create-a-ruby-api-with-sinatra/">https://x-team.com/blog/how-to-create-a-ruby-api-with-sinatra/</a></li><li><a href="https://www.discoverdev.io/blog/series/js30/">https://www.discoverdev.io/blog/series/js30/</a></li><li><a href="https://daveceddia.com/react-practice-projects/">https://daveceddia.com/react-practice-projects/</a></li><li><a href="https://medium.freecodecamp.org/how-to-build-a-react-js-chat-app-in-10-minutes-c9233794642b">https://medium.freecodecamp.org/how-to-build-a-react-js-chat-app-in-10-minutes-c9233794642b</a></li><li><a href="https://codeburst.io/writing-a-crud-app-with-node-js-and-mongodb-e0827cbbdafb">https://codeburst.io/writing-a-crud-app-with-node-js-and-mongodb-e0827cbbdafb</a></li><li><a href="https://codeburst.io/learning-react-js-by-building-a-minesweeper-game-ced9d41560ed">https://codeburst.io/learning-react-js-by-building-a-minesweeper-game-ced9d41560ed</a></li><li><a href="https://github.com/karan/Projects">https://github.com/karan/Projects</a></li></ul><p>To prepare for live coding challenges, I used <a href="https://www.pramp.com/#/">Pramp</a> for mock interviews 3–4 times a week, which improved my performances by leaps and bounds.</p><p>I’ve written before on this topic in <a href="https://medium.com/launch-school/why-you-need-an-interview-script-b86e18d0200a">Why You Need an Interview Script</a>, but essentially when under pressure our mental abilities can suffer due to the feeling of being evaluated. The best way to combat this issue is to have mock interviews to recreate the experience until we’ve adjusted to it. Having a problem solving process also really helped to give me a leg up, and the best one that I’ve found is <a href="https://medium.com/launch-school/solving-coding-problems-with-pedac-29141331f93f">PEDAC</a>.</p><h3>Know what you’re looking for in a role &amp; company</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4yMpTIs2F_svLXmDhgndbw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/k-xKzowQRn8?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Thom Holmes</a> on <a href="https://unsplash.com/search/photos/journal?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>With all that said, it’s important to take the time and consider exactly what you’re looking. Do you have a strong preference between backend, frontend, or full stack positions? How big of a company do you want to join? Which industries interest you? And in which direction do you want to grow your career?</p><p>Your answers to these questions can have a dramatic effect on which companies you choose to interview with. As software developers, we’re lucky to have no shortage of jobs and companies looking to hire, but it’s important to remember these points:</p><ol><li>There is a large variety of roles and areas of work to choose from, and you should consider which areas of software development you want to specialize in.</li><li>You should try to find a role and company that you’ll be happy to work in for several years. My personal opinion is that it’s important to build your experience, credibility, and professional network as an engineer and it’s best to work 1–2 years minimum in each role, rather than job hopping every 6 months — 1 year.</li><li>Just as there are a lot of good jobs in software, there are also a lot of bad jobs that you want to avoid. Not every job will have you work on mature, experienced teams building ambitious, challenging projects. There are jobs in which you could mainly handle tedious tasks, clean up legacy code, or simply minor UI components day-in &amp; day-out.</li></ol><p>So take the time to think about what you want and list the things that you look for in your dream job. For myself, I wanted a role that focused mainly on backend development with the opportunity to:</p><ul><li>Learn a compiled language like Go.</li><li>Work on distributed systems and possibly microservices.</li><li>Join an experienced team of engineers to learn from.</li><li>Have the ability to work remotely from time-to-time.</li><li>Work at a company that values diversity and inclusion.</li><li>Have benefits toward continued education.</li></ul><p>I aggressively sought out companies that offered most of them and didn’t spend time applying to those that didn’t. While not every company would have everything I was looking for, I knew that I would be happier with the end result than if I just mass applied everywhere.</p><p>A side benefit was that by targeting the specifics of my next role, I was able to focus my studies on relevant topics that allowed me to improve with every interview, which I feel gave me the needed edge to land my role at DigitalOcean.</p><h3>Manage the interview cycle</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z_8tiXSzygrOwlWXC0wxUw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/bwki71ap-y8?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Tim Gouw</a> on <a href="https://unsplash.com/search/photos/job?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>The interview process for software development is grueling, and the potential for burn out is very high. Typically, the process can comprise of 3–5 steps, or even more, like so:</p><ul><li>Initial phone screen with HR or a recruiter</li><li>Phone call with a company engineer or hiring manager</li><li>Live code challenge with a company engineer</li><li>Take home project</li><li>Onsite at the company</li><li>Potential offer extended</li></ul><p>Exhausting, right? And every company is different, with some having only 1–2 interviews before the onsite and others taking months!</p><p>From my job hunt, I experienced a cycle that repeated itself. First, I would have initial phone screens with multiple companies. These would then lead to code challenges, take home projects, or technical phone screens. After several of these steps and opportunities getting filtered out, any onsites would get clustered into the same week or two.</p><p>Since the intensity of these stages increased the further I went in the process, I had less time for new applications due to increased studying, culminating with my onsites which had me studying full-time without sending fresh applications. If no suitable offers were extended, then I would start again with fresh applications and the cycle would start over.</p><p>Here are some tips when going through this cycle:</p><ul><li>Try to keep your application activity high throughout the cycle. It’s important to keep applying and doing outreach in order to fill your interview funnel with new opportunities.</li><li>Have a daily goal of applications and outreach to complete. My daily goal for Monday-Thursday was to submit at least 5 applications (often with cover letters) and reach out to 5 engineers for coffee or to ask about open positions.</li><li>Think critically about what to expect in each interview. You may get some details in your initial phone screen about the interview process, but always ask for more info in order to prepare.</li><li>If you have a call with a CTO, know that it’s common for them to ask you technical questions regarding your resume as well as behavioral questions.</li><li>Don’t schedule onsites on back-to-back days. They are by far the most exhausting steps and need more preparation. Always give yourself at least one day of rest in-between onsites to recharge, review topics, and mentally prepare.</li></ul><h3>Avoiding burnout through the process</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/380/1*3QVuXfNawq8dGKfkXbs3eA.gif" /></figure><p>At this point, I want to address the importance of avoiding burn out during the job hunt. With the sheer number of interviews to complete and associated stress, it can easily feel overwhelming at times.</p><p>Don’t overwork yourself by studying &amp; coding for 6+ hours a day on top of interviews, and dedicate time each week to disconnect and recharge. It’ll help you maintain your energy &amp; focus as you steadily ramp up the intensity of later stage interviews.</p><p>At most, I studied 4 hours a day and prioritized deep work as described in Cal Newport’s <a href="https://www.amazon.com/Deep-Work-Focused-Success-Distracted/dp/1455586692">Deep Work</a>, which is where you focus intensely for a period of time on a task that is more difficult than what you’re used to without any distractions.</p><p>This meant solving algorithm problems or practicing projects that were harder than what I had already completed. This made sure that I kept improving my skills, while also identifying where I struggled and needed to study more.</p><p>And no matter how busy my week was, I always took at least one day off to relax and recharge for upcoming interviews.</p><h3><strong>In the end…</strong></h3><p>I’m extremely happy with the results of my job hunt and feel that the approaches I detailed above worked well for me. For those of you out job hunting now, I hope that this article proves helpful to you. I also recommend reading the following article, which I found very helpful for my job hunt:</p><p><a href="https://hackernoon.com/what-it-took-to-land-my-dream-software-engineering-job-17c01240266b">What it took to land my dream software engineering job — Sun-Li Beatte</a>ay</p><p>Good luck to everyone out there job hunting, keep it up!</p><p>Please let me know what you think in the comments! I’d love to hear more about your job hunt experiences and what has worked for you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b37bf3d0d630" width="1" height="1" alt=""><hr><p><a href="https://medium.com/free-code-camp/how-i-navigated-the-job-hunt-and-landed-my-dream-job-b37bf3d0d630">How I navigated the job hunt and landed my dream job</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 practical guide to containers]]></title>
            <link>https://medium.com/free-code-camp/a-practical-guide-to-containers-dfa66d37ac30?source=rss-54c5cb7f84d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/dfa66d37ac30</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Julius Zerwick]]></dc:creator>
            <pubDate>Fri, 11 Jan 2019 19:56:47 GMT</pubDate>
            <atom:updated>2019-01-28T16:20:31.730Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BNdwczuGtUJQLjgi2EaxZg.jpeg" /><figcaption>Photo credit: <a href="https://unsplash.com/@ant0ine">Antoine Petitteville</a> on Unsplash</figcaption></figure><p>Containers have taken over the software world by storm — and for good reason.</p><p>They’ve proven vital for DevOps and deployment, and have a multitude of uses for developers. And this goes not only for large companies, but for independent developers as well. In fact, containers played a vital role in the development and deployment of our project <a href="https://spacecraft-repl.com/">SpaceCraft</a>.</p><p>In this article, we’re going to give an introduction to containers and explain their core features. We’ll then showcase their uses in software development and cover some important topics regarding security and resource management. Along the way, we’ll give a peek into <a href="https://spacecraft-repl.com/whitepaper#5-security--resource-management-with-containers">how containers were utilized in SpaceCraft</a>. Let’s dive in!</p><h3>What Is A Container?</h3><p>So what exactly is a container?</p><p>At its core, a container can be described as a single unit of encapsulated software. It’s essentially a box in which you can place all of your project dependencies and run a single service or an entire development environment, while keeping everything inside the box isolated from the host system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yvWotn70SyhmChBl" /></figure><p>As an example, imagine that you need to work on a new project and know all of the needed dependencies. But some of these dependencies may conflict with what you already have installed on your computer, like a language version number.</p><p>If you were to work on the project on your computer, you’d have to go through the tedious process of managing your dependencies and deactivating versions while activating the versions that you need.</p><p>This issue is compounded when it’s a whole team of developers working on the same project, and no two developers have the same configurations on their computer.</p><p>With a container, you can simply put all your needed dependencies inside it and then work on your project from within the container. This saves a ton of a headache by eliminating the dependency management issues and instead providing us with an isolated area to work in.</p><h3>How are containers made?</h3><p>So we now know what a container is. But how exactly do we create them?</p><p>Well, to start we need to create an image. This is simply a package that includes all of the dependencies that should exist in our container. It’s a snapshot of everything that should be inside our container when we run it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*scsKCR90km2tHBVt" /></figure><p>An easy way to visualize this is to think of an image as a class and a container as an object that is instantiated from that class. So our image will serve as a blueprint for creating our containers, and we can create any number of identical containers from the same image.</p><h3>How are images built?</h3><p>Images are built by <a href="https://www.aquasec.com/wiki/display/containers/Docker+Images+101">executing a set of commands</a>. In Docker, the set of commands are written in a text file called Dockerfile.</p><p>When the image build process starts, each command <a href="https://docs.docker.com/storage/storagedriver/#images-and-layers">forms a layer</a> that comprises the final image. The last layer specifies what command to run within a container when a container is started.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EwCkQvNdRGkNLRPv" /><figcaption>An example Dockerfile that builds into an image. Each layer represents an instruction from the Dockerfile.</figcaption></figure><p>In <a href="https://spacecraft-repl.com/">SpaceCraft</a>, we bundled a <a href="https://hub.docker.com/r/phusion/baseimage/">modified version of Ubuntu</a>, our language runtimes, and a copy of our application code into an image to start multiple containers that each run an instance of our application.</p><p>Images do not necessarily need to be stored or built on just your local machine. Containers are meant to be deployable anywhere and thus we should be able to access our images from any physical machine. This is accomplished through <a href="https://docs.docker.com/registry/introduction/#understanding-image-naming">registries</a>, which are essentially a place to remotely store and access images.</p><h3>Why should we use containers?</h3><p>Now we can dive into the many use cases of containers.</p><p>Remember how we said that containers can provide us with an isolated box to hold a development environment with a specific set of dependencies? Each developer can simply download the needed image from a registry onto their local computer and then create a container from that image.</p><p>This way, they can start contributing to existing projects in no time.</p><h4>Ease of deployment</h4><p>As you can see, one of the biggest advantages of containers is that they are easily deployable on a variety of systems, due to their isolation. This allows developers to uncouple their software from their physical machines and launch a container from anywhere.</p><h4>Run multiple services on one machine</h4><p>Another use case involves placing a single service in a container and then communicating with that service.</p><p>In this situation, you can build a system that houses individual services in separate containers. This allows you to isolate each piece of your system architecture and run multiple services on the same host while making it easy to swap services in and out of your system as needed.</p><p>To demonstrate how this works, each service can communicate with each other through <a href="https://docs.docker.com/v17.09/engine/userguide/networking/">Docker container networking</a> by their IP addresses. With this, containers can, for instance, send HTTP requests with the destination container’s IP address as part of the URL.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/874/1*iWhuxKeM7ydMfZQb2GQLkA.png" /><figcaption>Containers can communicate with each another via their IP addresses.</figcaption></figure><p>In fact, we use this technique in <a href="https://spacecraft-repl.com/">SpaceCraft</a>. We’ve built a <a href="https://www.incapsula.com/cdn-guide/glossary/reverse-proxy.html">reverse proxy server</a> that forwards clients’ requests to the appropriate containers. To enable communication between our reverse proxy server and the containers, we retrieve the containers’ IP addresses during initialization and use them as destinations for proxying.</p><h4>Isolation for Security</h4><p>Another important use case is that containerized applications are isolated from the host system. This prevents unwanted user access to the host’s file system. This is important, especially for an application like <a href="http://repl.space/">SpaceCraft</a> that gives users the ability to execute code.</p><p>We can also add security measures to strengthen the isolation and further prevent malicious activity from reaching our host system. We’ll explore these strategies in the following section.</p><h3>Containers versus Virtual Machines</h3><p>At this point, we want to make clear the distinction between containers and virtual machines, as this can heavily impact your decision on which to use.</p><p>Virtual machines came before containers, and were used to address the same pain points as containers. Essentially, they provide an isolated environment for services and development and are deployable on multiple systems.</p><p>However, there are some significant differences between them and containers.</p><h4>Containers are more lightweight, and faster to spin up</h4><p>First, containers are more lightweight in memory requirements than virtual machines. Depending on what you place in a container, they generally run in the tens to hundreds of MBs for memory size.</p><p>Virtual machines are far heavier and run into the GBs. This is mainly due to one big inclusion: the operating system kernel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*a8oStcuvBWIU9Vx6.png" /><figcaption>Source: <a href="https://blog.octo.com/en/i-am-a-developer-why-should-i-use-docker">I am a Developer: why should I use Docker?</a></figcaption></figure><p>Virtual machines contain not only all of your dependencies for your service or environment, but also a full copy of an operating system kernel to run all of your dependencies. This addition can add a lot of memory to an instance of a virtual machine.</p><p>On the other hand, containers don’t contain a kernel and instead make system calls to the host system kernel. This dramatically lowers their memory footprint. It allows for more containers to be created and used on a system, as opposed to the number of virtual machines you can run on the same system.</p><p>In addition to a smaller memory footprint, the lack of a kernel in a container makes their startup time a lot faster. Container startup can happen in seconds, whereas virtual machines will take much longer.</p><h4>VMs are more secure by default</h4><p>However, there are always tradeoffs. When it comes to virtual machines versus containers, the big tradeoff is security.</p><p>Because containers need access to the host system kernel to make system calls, they are not as airtight on security as a virtual machine.</p><p>In fact, resourceful malicious users can find ways to use this security disadvantage to break out of a container and gain access to the host system.</p><p>With virtual machines, this risk is mitigated because each instance of a virtual machine contains a kernel for its system calls. Thus there is stronger isolation between a virtual machine and the host system than with a container.</p><p>However, the security risks of containers can be addressed by implementing a few security measures that we incorporated into <a href="https://spacecraft-repl.com/">SpaceCraft</a>, which we will look at now.</p><h3>Security measures</h3><p>One huge security issue that you should know about is that users generally run as root users in containers by default.</p><p>This means that anyone who works inside a container, whether a developer on your team or a user who is using an application that is housed in a container on the back end, will have privileged access to the container file system.</p><p>If you’re concerned about giving this level of control over to the container user, then you should consider ways to limit their privileges.</p><p>This issue can be addressed by creating an unprivileged user profile in the container filesystem, and having users run as that user profile while in the container.</p><p>This will restrict their ability to access the container filesystem and run commands that could harm your container environment and any services running inside it.</p><p>Another security issue that can rear its head is the ability for users to break out of containers and access the file system of the host system.</p><p>As we mentioned before, containers make system calls to the host system kernel in order to run processes. This opens the door for malicious users to break out of a container and attach the host system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1foYXcmqkxT5MF_z" /><figcaption>Containerization alone provides weak isolation, where all system calls made by our application are accepted by the host kernel. Source: <a href="https://github.com/google/gvisor">gVisor Github</a></figcaption></figure><p>One of the methods we use to prevent this situation is to use a container runtime sandbox to intercept the system calls made by a container. The sandbox acts as a guest kernel and creates a strong level of isolation between the container and host kernel. This prevents malicious users from attacking our host system.</p><p>If you’re interested in using a container runtime sandbox, check out <a href="https://github.com/google/gvisor">gVisor</a> which is an open-source solution provided by Google that we utilized with <a href="https://spacecraft-repl.com/">SpaceCraft</a>.</p><h3>Container resource control</h3><p>One more issue that we want to address pertains to potential abuse of a container’s resources.</p><p>Since a container runs on a host system and uses the host kernel, it essentially consumes CPU and memory resources from the host system to complete its processes and tasks.</p><p>While this is usually not a problem on an individual level with developers using containers, it does become a bigger problem once we use containers to deploy applications to be used by external users.</p><p>Let’s say that your system architecture includes using containers to run separate instances of your application that users can access. And something happens with one of those containerized instances that requires more CPU and memory from the host system than expected.</p><p>What this can result in is that one instance hogs system resources away from the other instances which causes their performances to drop and create a poor user experience.</p><p>Obviously, this is a situation that we want to avoid if possible. Thankfully we can do so with cgroups, which is short for ‘control groups’.</p><p>With cgroups, you can limit the amount of system resources used by a container and thereby prevent the situation we just described.</p><p>For example, you can set the cgroups on a container to be a maximum of 100MB of memory and 20% of CPU. With those limits set, that container will never be able to use more than 100MB of memory or utilize more than 20% of CPU from the host system for its lifetime. You can rest easy knowing that the performance of your other containerized application instances will not drop.</p><p>In SpaceCraft, we utilized cgroups to limit the maximum amount of memory and CPU that a single session can consume. If a session happens to run an expensive computation and consume all available resource within that container, only that session will be affected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4AuQsNiYE-xTqP5z" /><figcaption>With each session isolated and controlled through cgroups, a single spike in resource consumption will only affect that session, while leaving others unaffected.</figcaption></figure><h3>Where can I get started?</h3><p>There are many container services that you can choose from. We used Docker for <a href="https://spacecraft-repl.com/">SpaceCraft</a> due to its ease of use and excellent documentation. We highly recommend it for your next project.</p><p>Other options include:</p><ul><li>Redhat OpenShift</li><li>Amazon EC2 Container Service</li><li>AWS Elastic Container Registry</li><li>Google Cloud Container Registry</li><li>Azure Kubernetes</li><li>HashiCorp</li><li>Quay</li></ul><h4>Integration with Node.js</h4><p>If you use Node.js primarily for your development, <a href="https://github.com/apocas/dockerode">Dockerode</a> can help you to interact with Docker from within a Node.js environment. We leveraged Dockerode to help us perform some important container actions, including:</p><ul><li>Starting and destroying a container</li><li>Reading a container’s IP address</li><li>Placing limits on a container’s memory and CPU usage</li></ul><p>Those operations are important to help us handle multiple sessions and scale our application.</p><h3>Conclusion</h3><p>Containers are an extremely useful tool in your arsenal as a software developer to simplify and speed up your project deployment.</p><p>Whether it’s creating an isolated development environment for building projects, setting up a microservices architecture, or helping to onboard a new team member, the utility of containers continues to grow over time. Give it a try in your next project and see how they can benefit you!</p><p>If you enjoyed reading this article, we’ve also written a<em> </em>detailed case study on how we built SpaceCraft and the challenges that we faced. You can<strong> </strong><a href="https://spacecraft-repl.com/whitepaper"><strong>read it here</strong></a><strong>.</strong></p><p><em>Co-written by Julius, Gooi, and Nick of the </em><a href="https://spacecraft-repl.com/team"><em>SpaceCraft Team</em></a><em>.</em></p><h3>References</h3><p>- <a href="https://www.docker.com/resources/what-container">What is a container</a><br>- <a href="https://blog.octo.com/en/i-am-a-developer-why-should-i-use-docker/">I am a Developer: why should I use Docker?</a><br>- <a href="https://dev.to/petermbenjamin/docker-security-best-practices-45ih">Docker Security Best-Practices</a><br>- <a href="https://cloud.google.com/blog/products/gcp/open-sourcing-gvisor-a-sandboxed-container-runtime">Open-sourcing gVisor, a sandboxed container runtime</a><br>- <a href="https://devops.stackexchange.com/questions/447/why-it-is-recommended-to-run-only-one-process-in-a-container">Why it is recommended to run only one process in a container?</a><br>- <a href="https://medium.com/@mccode/processes-in-containers-should-not-run-as-root-2feae3f0df3b">Processes In Containers Should Not Run As Root</a><br>- <a href="https://pubs.vmware.com/vsphere-4-esx-vcenter/index.jsp?topic=/com.vmware.vsphere.server_configclassic.doc_40/esx_server_config/security_for_esx_systems/c_security_and_virtual_machines.html">Security and Virtual Machines</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dfa66d37ac30" width="1" height="1" alt=""><hr><p><a href="https://medium.com/free-code-camp/a-practical-guide-to-containers-dfa66d37ac30">A practical guide to containers</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[My List of Books & Resources for LS Students]]></title>
            <link>https://medium.com/launch-school/my-list-of-books-resources-for-ls-students-72e468c41188?source=rss-54c5cb7f84d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/72e468c41188</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[launch-school]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Julius Zerwick]]></dc:creator>
            <pubDate>Mon, 07 Jan 2019 21:58:40 GMT</pubDate>
            <atom:updated>2019-01-07T21:58:40.544Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cbj_BcK5ePD4Mc4TK4sfvQ.jpeg" /></figure><p>In this blog post, I want to provide a list of books and resources that I’ve found useful as I worked through the Launch School core curriculum and Capstone. I’ll focus on the ones that I feel are most relevant for the general reader (a student in the core curriculum or Capstone) while also avoiding niche topics that may be too specific (such as containers, P2P architecture, NoSQL databases, etc).</p><p>The rule of thumb that I used for selecting these resources is that it needed to run parallel with the course that I was currently studying, while giving me some needed depth on the course material. All links to the resources are accessible by clicking the resource title.</p><p>And with that, here we go!</p><h3>Ruby</h3><p>The resources that I chose for Ruby were fewer than the other areas, and that’s mainly because the LS curriculum covers a ton of the material for you. Additionally, the first two courses in the core (101, 120) can feel overwhelming in the beginning with all the information they cover and I didn’t want to tack too much on top of them.</p><h4><a href="https://www.amazon.com/Eloquent-Ruby-Addison-Wesley-Professional/dp/0321584104">Eloquent Ruby</a></h4><p>This is a fantastic book to read through after finishing the 101 &amp; 120 courses in the core. Russ Olsen provides a good breadth of topics and serves as a welcome refresher if you find yourself getting rusty on Ruby over time. I also found the writing to be clear and the author to do a great job of keeping you engaged. Additionally, it serves as a good reference by giving you concise, self-contained chapters on topics while also telling you where you can get into trouble with the topic and how to avoid it. The first half of the book will be relevant to LS students and the second half can be read if you want to take your Ruby skills further.</p><h4><a href="https://www.bloc.io/ruby-warrior#/">Ruby Warrior</a></h4><p>I love this game! It’s a fantastic way to practice your OOP skills in the 120 course and to prepare for the 129 assessment, and the difficulty ramps up after a few levels. While you can get through the first few levels with some large conditionals to handle the obstacles, you’ll quickly find yourself having to refactor your code to handle the more complicated levels. The reason that I chose this resource is that while 120 provides a lot of great material, I found myself needing some more practice writing OO code to solidify the concepts and this game addressed that need fairly well. This game provided that for me while also being more difficult than any examples I could come up with on my own. Plus it’s loads of fun!</p><h3>JavaScript</h3><p>Just as with 101 &amp; 120, the LS courses covering JavaScript do an excellent job of teaching what you need to know. With JavaScript, I reached for resources that helped me understand the many quirks of the language or supplement certain areas of the last few courses in the core curriculum.</p><h4><a href="https://www.amazon.com/JavaScript-Good-Parts-Douglas-Crockford/dp/0596517742/ref=sr_1_1?s=books&amp;ie=UTF8&amp;qid=1546642700&amp;sr=1-1&amp;keywords=javascript+the+good+parts">JavaScript: The Good Parts</a></h4><p>This book is excellent in concisely explaining the good parts of JavaScript and includes sections on the bad &amp; awful parts to avoid. I’ve had many people say that this book helped further their understanding of the language and prepare them for interview questions on JavaScript, and I completely agree with them. LS gives you the core of what you need to know, and Douglas Crockford takes you further by really targeting the important topics to review and know. All in a wonderfully small book!</p><h4><a href="https://nodeschool.io/">NodeSchool</a></h4><p>NodeSchool is a free collection of workshops that you can download to learn JavaScript and Nodejs, the latter of which is extremely important if you want to learn full-stack JavaScript. Nodejs is a JavaScript runtime designed to run on the server and has many topics that aren’t fully covered in the LS courses like using promises, accessing stdin/stdout streams, using npm, and many more.</p><p>For students in the core curriculum, NodeSchool has workshops that pair nicely with the LS JavaScript courses and provide exercises to practice your skills before tackling the assessments and projects. Relevant workshops cover basic JavaScript, debugging, prototypes, scopes &amp; closures, and testing. If you find yourself needing more practice with JavaScript or targeted learning of certain topics, I highly recommend using NodeSchool. And once you’ve completed the core curriculum, check out the Nodejs workshops as Nodejs is an extremely popular technology and has often been used in many Capstone projects.</p><h4><a href="https://github.com/getify/You-Dont-Know-JS">You Don’t Know JS: Book Series</a></h4><p>This series is a monster, and I would only recommend it once you’re preparing for the 239 assessment or have finished the front-end courses. There are six books in the series (all free to read online) and the author Kyle Simpson peels back the many layers of abstractions that come with JavaScript. What I really appreciate about this series is that each book is fairly self-contained, so you can dive into the areas that you wish to learn about. In particular, there is an entire book on <a href="https://github.com/getify/You-Dont-Know-JS/blob/master/es6%20&amp;%20beyond/README.md#you-dont-know-js-es6--beyond"><em>ES6</em></a>, which completes the LS curriculum nicely as ES6 isn’t deeply covered in the last course (at least at the time of writing this article). There is also a separate book on<a href="https://github.com/getify/You-Dont-Know-JS/blob/master/this%20&amp;%20object%20prototypes/README.md#you-dont-know-js-this--object-prototypes"><em> this &amp; Object Prototypes</em></a> that I found useful to understand what I felt was one of the hardest concepts when learning JavaScript. And once you’ve finished the core curriculum/Capstone, look more into these books. I consider them to be part of a “finishing school” for students who wish to learn JavaScript extremely well.</p><h3>Terminal</h3><p>The terminal/shell is an essential tool in every developers arsenal. It’s our work bench for building projects, running code, debugging, monitoring, and so much more. And as you start developing whole systems with remote components, you’ll need to be extremely comfortable with working solely on the command line. As developers, our craft depends on knowing our tools extremely well and learning how to operate your computer (and in the future whole systems) from the terminal will pay large dividends in your future career.</p><p>For most LS students in the core curriculum, their use of the command line will often be navigating the file system, creating and deleting files/directories, using Git &amp; Github, and working on projects. This is fine and the first two resources below will be the most relevant. For students who wish to go further or students wishing to do Capstone, the last two resources will be pretty helpful as they start building projects that require them to use remote servers, handle multiple processes, access the std/stdout streams, and much more.</p><h4><a href="https://thoughtbot.com/upcase/mastering-the-shell">Mastering the Shell</a></h4><p>This course is a brief intro to topics of the shell that go beyond the LS command line book. The benefit is that you’ll see how powerful it can be and that there are a lot of tasks that you can do without needing Ruby or JavaScript. This course is also a good way to get context for the following resources, plus it can all be completed in a day (and yes, the irony of a course titled “Mastering the Shell” that can be completed in a day is not lost on me, but it’s still worth a look).</p><h4><a href="https://github.com/jlevy/the-art-of-command-line">The Art of the Command Line</a></h4><p>This is a big cheatsheet of things to know regarding the command line. The basics and everyday sections are great for making you more aware of what you can do from the terminal and I’ve learned a lot of useful tricks from it.</p><p>It’s mainly to help you become more efficient with using the command line in your everyday tasks. I wouldn’t recommend going through it all at once since there is a lot of breadth and many of the points can lead to potential rabbit holes. Look through the basics and everyday sections, and come back to this cheatsheet over time.</p><h4><a href="https://github.com/icevans/linux-study-group">LS Linux Study Group</a></h4><p>Once you’ve got a handle of the basics and see the motivation for mastering the terminal, I recommend that you check out the LS Linux Study Group. Started by fellow student Ian Evans, the group is a fantastic resource for furthering your learning of the terminal, shell, and Linux with a curated list of topics to study and fellow students ready to help each other learn. There is also a slack channel you can join to discuss the topics together!</p><h4><a href="http://linuxcommand.org/tlcl.php">The Linux Command Line</a></h4><p>This is one of the main resources used in the LS Linux Study Group and for good reason. Going through this book will greatly improve your knowledge of the command line and help you realize how much control you can have over your computer and systems, and the author has generously provided it for free online.</p><p>Before Launch School, I used my computer mainly for schoolwork, internet browsing, and social media for ~25 years and viewed it mainly as a “black box”. But LS combined with this book and the resources above truly show how much control you can have in actually “driving” your computer as you see fit. Parts 1 + 2 will be relevant for many LS students, and parts 3 + 4 are good reference sections for future studies and projects. I’d recommend that you check this book and the LS Linux Study Group out after finishing the 170 course.</p><h3>Algorithms &amp; Data Structures</h3><p>Now we come to algorithms and data structures, which are vital to learn for not only job interviews but also to step up to the next level as a developer. The resources listed here provide the background and context, and the next section on practicing code challenges will provide you with opportunities to use them. Look into these resources once you’ve finished the core curriculum or are about to start Capstone.</p><h4><a href="https://medium.com/basecs">BaseCS</a></h4><p>This blog series is a slam dunk and I’m obsessed with it. Vaidehi Joshi spent a whole year writing about algorithms &amp; data structures and each article contains a wonderful amount of depth. There isn’t any code in the articles, but you’ll learn the background about a data structure/algorithm, how and why it’s used, and the tradeoffs of using them. I used this series to gain the background information needed to start solving coding challenges.</p><p>Note: The author has recently started a new blog series called <a href="https://medium.com/baseds/many-nodes-one-distributed-system-9921f85205c4">BaseDS</a> that delves into distributed systems every alternate Wednesday. Her first article is out and can be found <a href="https://medium.com/baseds/many-nodes-one-distributed-system-9921f85205c4">here</a>.</p><h4><a href="https://www.amazon.com/Common-Sense-Guide-Data-Structures-Algorithms/dp/1680502441/ref=sr_1_1?ie=UTF8&amp;qid=1546643140&amp;sr=8-1&amp;keywords=a+common+sense+guide+to+data+structures+and+algorithms">A Common Sense Guide to Algorithms</a></h4><p>This book is similar in many ways to the BaseCS series in that it provides the background information on algorithms and data structures. The reason for its inclusion in this list is that each chapter has code implementations of the covered topic and I’ve found it helpful in my learning to read different approaches to new topics. It’s another useful resource for bridging the gap between having the knowledge of a data structure/algorithm and then being able to use that knowledge to solve problems and develop projects. Also, this book has been part of the Capstone curriculum (at the time of writing this article) so its been thoroughly vetted and its worth can be attested to.</p><h4><a href="https://www.geeksforgeeks.org/">GeeksforGeeks</a></h4><p>This website is extensive in its offerings of information of data structures and algorithms. Along with informative articles, there are coding challenges with solutions and suggested projects to practice using the knowledge you’ve gained from the previous two resources. I consider GeeksforGeeks as a step up from BaseCS and A Common Sense Guide to Algorithms due to its use of more technical language and heavy use of Java &amp; C++ solutions to problems (though many problems do have a Python solution). This isn’t a true barrier to LS students but I have found that it requires more time for me to work through the unfamiliar language syntax. Just remember, no matter the language a loop is still a loop, a conditional is still a conditional, and so on.</p><h3>Practicing Code Challenges</h3><p>So now we come to solving problems with all the knowledge you’ve acquired! Here are some of my favorites sites for practice that can be used during the core curriculum for extra practice or to prepare for the job hunt.</p><h4><a href="https://leetcode.com/problemset/all/">LeetCode</a> &amp; <a href="https://www.codewars.com/">CodeWars</a> &amp; <a href="https://exercism.io/">Exercism</a></h4><p>These sites list hundreds of problems with provided test cases, and many have solutions for you to learn from. What I especially like about LeetCode is that it also categorizes problems based on data structures, so you can focus your time on the topics that you need to practice. Additionally, many companies pull their interview questions directly from LeetCode and its not unheard of for developers to solve one of their problems, then walk into the interview and be given the exact same problem.</p><h4><a href="https://projecteuler.net/archives">Project Euler</a></h4><p>Another useful site for practicing your problem solving skills with a focus on mathematics. I once read an article that advocated for developers to solve the first 50–100 problems on this site in whatever language they’re learning in order to cement the language syntax and intricacies, and I think it’s an excellent idea.</p><h4><a href="https://www.discoverdev.io/blog/series/js30/">JS30 Series</a></h4><p>This series consists of 30 small projects for targeting those HTML/CSS and JavaScript skills. The 230 course on DOM &amp; Asynchronous JavaScript contains a ton of projects and exercises to practice the material, and I still found these projects helpful to add. There are a lot of concepts coming together and mixing when you start making dynamic web apps and handling user events, and I found that the more projects you complete for practice the greater your skills and confidence will become.</p><h3>System Architecture &amp; Networking</h3><p>This final area is for students who have either completed the core curriculum, started doing Capstone, or have enough spare time on their hands to consider learning more about system architecture and networking. These resources will help introduce you to the wider world of programming and designing complete systems, and are helpful for learning exactly how web apps come together with their various components.</p><h4><a href="https://hpbn.co/">High Performance Browser Networking</a></h4><p>This book is amazing, and the author Ilya Grigorik has generously made it available for free in an online format. I’ve learned so much about browser networking, HTTP, TCP/IP, latency, bandwidth, optimizations, and much more from this book, and consider it instrumental to bridging the gap between the core curriculum and Capstone or the job hunt. But even before that, you’ll find chapters helpful for certain LS courses.</p><p>It provides a depth of information on HTTP and TCP/IP for students in the 170 course, describes techniques for optimizing the delivery of assets to decrease the latency of web apps for students in the 230 course, and has sections on relevant technologies like WebSockets, WebRTC, etc. Personally, I have found this book to be a cornerstone to the success of my team’s Capstone project <a href="https://spacecraft-repl.com/">SpaceCraft</a>.</p><h4><a href="https://engineering.videoblocks.com/web-architecture-101-a3224e126947">Web Architecture 101</a></h4><p>This blog gives a nice overview of the many architecture components that make up a web app like web servers, caches, content delivery networks (CDNs), job queues, and more. It helps you see the high-level design of web apps and describes how each component fits into that design.</p><h4><a href="https://github.com/donnemartin/system-design-primer">System Design Primer</a></h4><p>After reading the Web Architecture 101 blog, check out this Github repo on system design. It takes each of the components in the above blog and provides tons of more information, as well as the tradeoffs of using each component. It also has case studies of systems used by Dropbox, Uber, Facebook, and more that will prepare you for system design interviews during the job hunt.</p><h3>Exclusions</h3><p>Now that I’ve provided my recommendations, I wanted to go over a list of books that I’ve either seen tossed around among LS students or find mentioned in many popular lists of “Books Every Programmer Should Read”, but that I would NOT recommend you read at this time. I’ll explain why as well as when you should use them below.</p><h4><a href="https://www.amazon.com/Well-Grounded-Rubyist-David-Black/dp/1617291692/ref=sr_1_1?s=books&amp;ie=UTF8&amp;qid=1546642764&amp;sr=1-1&amp;keywords=well+grounded+rubyist">The Well-Grounded Rubyist</a></h4><p>This is a great book and its part of many lists for books that every Ruby developer should read. I actually used to recommended this book to other LS students while I was in the 101 &amp; 120 courses, but I’ve stopped doing so. The reason that I’ve made it an exclusion is that it both goes into way too much depth and many of the topics are already covered extensively by the 101 &amp; 120 courses. So it essentially repeats a lot of the material that you’ll learn in those courses and each of the chapters are pretty beefy to get through. I’d recommend this book as a reference for the future if you find yourself working with Ruby.</p><h4><a href="https://www.amazon.com/Practical-Object-Oriented-Design-Ruby-Addison-Wesley/dp/0321721330/ref=pd_lpo_sbs_14_t_2?_encoding=UTF8&amp;psc=1&amp;refRID=E4V2T95ET51G9R96WHAZ">Practical Object-Oriented Design in Ruby</a></h4><p>Here is another popular book for Ruby developers and for good reason. Sandi Metz is a fantastic teacher and really breaks down how to write good OO code. However, this book lands in that area of being more useful for working developers rather than LS students since it’s aimed to teach you how to break bad habits, spot troublesome patterns, and work with OOP in a newer, better light. Some of the topics covered in the book are things that sound like a good idea if you’ve never seen them before, but will only truly hit home once you’ve felt the pain of writing or working with bad/problematic OO code. It’s on my bookshelf for my career, but not for the LS core curriculum.</p><h4><a href="https://eloquentjavascript.net/">Eloquent JavaScript</a></h4><p>This book faces the opposite problem of <em>The Well-Grounded Rubyist</em>. It teaches you JavaScript with the expectation that the reader has zero knowledge of the language, while also providing little material that goes beyond the LS courses. If you complete the LS JavaScript courses, then you’ll already have covered everything in this book and more.</p><h4><a href="https://www.amazon.com/Cracking-Coding-Interview-Programming-Questions/dp/0984782850">Cracking the Coding Interview</a></h4><p>This book is widely regarded as essential for the job hunt, and I agree. It provides a ton of problems to practice for interviews, describes what the interview process is like at the top tech companies (Facebook, Amazon, Microsoft, Google, Palantir), and even gives problem solving steps to add to PEDAC for optimizing your solution. However, this book is extremely narrow in its usefulness and unless you are about to start looking for a job then there is no need for you to pick it up. Once you do start job hunting, combine this book with LeetCode and GeeksforGeeks to maximize your practice.</p><h4><a href="https://www.amazon.com/Pragmatic-Programmer-Journeyman-Master/dp/020161622X/ref=sr_1_6?s=books&amp;ie=UTF8&amp;qid=1546642838&amp;sr=1-6&amp;keywords=programming+pearls">The Pragmatic Programmer</a>, <a href="https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882/ref=sr_1_1?s=books&amp;ie=UTF8&amp;qid=1546642814&amp;sr=1-1&amp;keywords=clean+code">Clean Code</a>, <a href="https://www.amazon.com/Programming-Pearls-2nd-Jon-Bentley/dp/0201657880/ref=sr_1_1?s=books&amp;ie=UTF8&amp;qid=1546642838&amp;sr=1-1&amp;keywords=programming+pearls">Programming Pearls</a>, <a href="https://www.amazon.com/Code-Complete-Practical-Handbook-Construction/dp/0735619670/ref=sr_1_3?s=books&amp;ie=UTF8&amp;qid=1546642878&amp;sr=1-3&amp;keywords=code+complete">Code Complete</a></h4><p>All of these books are fantastic and deserve a place on your bookshelf for your career. However, they have the same problem as <em>Practical Object-Oriented Programming in Ruby</em> — they are targeted toward improving professional developers, not newer developers still learning the fundamentals. These books are meant to make you a better developer at work and many of the lessons they cover are things which in my opinion you need to feel the pain of before you can appreciate their lessons. You have to learn things one step at a time, and these books are for that step you take after starting your career.</p><h3>Conclusion</h3><p>I hope that you find this list useful in your journey as a LS student. There are too many resources out there for anyone to completely go through and many require a specific point in your studies or professional life to be worth their value. The resources that I’ve listed here have been useful to me and I’ll likely come back to them in the future as I circle back on topics that I need to review.</p><p>What I would like to emphasize before closing out this blog is the following: always put your LS course before any of these resources (especially if you are pressed for time) and find what works best for you. Your priority should be mastering the LS material and acing the assessments, and while these resources are great they are no substitute for what LS has already created. Your journey toward being a professional software engineer is your own and you need to take ownership of it by using the resources that work for you.</p><p>If you have any comments, questions, or other recommendations, please leave them in the comments below! Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72e468c41188" width="1" height="1" alt=""><hr><p><a href="https://medium.com/launch-school/my-list-of-books-resources-for-ls-students-72e468c41188">My List of Books &amp; Resources for LS Students</a> was originally published in <a href="https://medium.com/launch-school">Launch School</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Elevate Your Learning]]></title>
            <link>https://medium.com/launch-school/elevate-your-learning-490a91d00584?source=rss-54c5cb7f84d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/490a91d00584</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[how-to-study]]></category>
            <category><![CDATA[launch-school]]></category>
            <category><![CDATA[learn-to-code]]></category>
            <dc:creator><![CDATA[Julius Zerwick]]></dc:creator>
            <pubDate>Mon, 12 Nov 2018 19:36:36 GMT</pubDate>
            <atom:updated>2018-11-12T22:42:18.107Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pnS4BMM1xGMYUGbtccyWmw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/CyvK_Z2pYXg?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Robert Bye</a> on <a href="https://unsplash.com/search/photos/study?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>In this article, I wanted to write about the changes I’ve made in my own ability to learn new subjects and material through my journey at Launch School. I think that it’s crucial for anyone in a knowledge-driven field to analyze how they learn and improve these skills, and that goes double for software developers.</p><p>Software development demands a near constant learning of new technologies and areas in order to stay sharp, stand on the forefront of technology, and remain hirable in the future. And thus it is vital that we not only learn new subjects deeply, but also improve our ability to learn more effectively.</p><p>Over the past 1.5 years of studying at Launch School, I’ve continually improved my learning process and revamped the techniques I use on a daily basis. I’ve gone through the Learning How to Learn course on Coursera and read multiple books that have influenced how I learn, which I’ve listed at the end of this article. I’d like to share with you what I’ve found useful and what I’ve discarded as useless. Let’s begin!</p><h4>Spaced Repetition</h4><p>This technique is a process in which you review material on a delayed time scale and is often implemented through flashcards. The goal is to review material that you find difficult more frequently, and to review material at the point that you’re just about to forget it. This helps to build a stronger neural connection to the information so that you can recall it more effectively.</p><p>Let’s say that you’re studying JavaScript and have created a flashcard deck covering everything you need to know about it. Traditionally, one would review the entire deck every time they study and they would review it every day or so.</p><p>Spaced repetition has you review the deck once, separate the cards based on whether you recalled the card’s info easily or not, and then review the cards again at different intervals. If you got a card right immediately, review it again in a week. If you struggled with a card, then review it tomorrow. Repeat this process over time and extend the intervals if you continually recall a card’s information. And if you struggle with a card, then “reset” it’s interval to tomorrow.</p><p>This technique requires consistency and offers huge payoffs by improving your ability to remember key information while also giving you a system to study a reasonable amount of cards each day. Thankfully, there is a free program called<a href="https://apps.ankiweb.net/"> Anki</a> that you can download to create and store your flashcards, and it even calculates the time intervals for you! I highly suggest you use it instead of keeping your own flashcards on hand.</p><h4>Deep Work</h4><p>This is a game changer and was made mainstream by Cal Newport in his book<a href="https://www.amazon.com/Deep-Work-Focused-Success-Distracted/dp/1455586692"> Deep Work</a>, which I highly recommend. The book’s key takeaway is that in order to thrive in the knowledge economy of today (which software development firmly sits in), we need to develop the ability to quickly master hard things and produce at a high level in terms of both quality and speed. And the way to do so is through deep work, which is when you work/learn in a state of distraction-free concentration that pushes your abilities to the limit.</p><p>For example, if you’re studying blocks in Ruby and want to utilize deep work, then you need to study somewhere quiet without any distractions (no social media, email, phone, music, etc.) and push your brain to soak in the information by filling in the gaps of your knowledge and solving problems. You’ll likely find that doing so will be hard as your focus will constantly want to shift to something new and your brain will feel strained by having all your concentration on the material.</p><p>However, this technique is extremely important as it builds your brain like a muscle. In the beginning, I couldn’t perform deep work for more than about 40 min at a time before I needed a break. But now I’m able to do 1.5 hours at a time 3–4x a day. There is a reason that deep work is often discussed at Launch School, as it truly improves your ability to learn a new topic and work through challenging situations.</p><p><strong>Deliberate Practice</strong></p><p>Another technique that is closely related to deep work is deliberate practice, which is the focused practice of a weak area/skill in order to improve it. Just like deep work, it requires you to work distraction free and to focus entirely on the task at hand. The task should be a challenge that is just above your current skill level in order to facilitate and push your growth. The steps I follow for deliberate practice are generally:</p><ol><li>Identify a weak area/skill that I need to improve.</li><li>Create a goal that I want to achieve by the end of my practice.</li><li>Work distraction free on this area/skill for a set amount of time (typically 1–1.5 hours is the limit for most people).</li><li>Review my progress and determine if I’ve met my goal.</li></ol><p>To make this more concrete, let’s use the example of me improving my front-end development skills in the 230 course. While in the course, I had identified that I felt struggled with building small projects from barebones HTML &amp; CSS all the way up to adding the user interactions with JavaScript. My deliberate practice would then be to:</p><ol><li>Identify that my weak skill was on building up the UI, not the HTML/CSS or basic JavaScript.</li><li>Set my goal to be a completed small project that allows user interactions through event listeners, handlers, &amp; managing HTTP requests.</li><li>Set up my work area to be removed of distractions and start with a barebones project that already had HTML/CSS and a backend to receive HTTP requests (there are plenty of such projects to practice with in the 230 course).</li><li>Work on this project for 1–1.5 hours with complete focus.</li><li>Once the time is up, I’ll quickly review my progress and determine what areas in the project I needed to practice further.</li></ol><p>You can use deliberate practice on almost any subject or project so long as you follow a similar process. Soon enough, you’ll see a considerable improvement in what was once a weak area for you.</p><p>I do want to make a quick note of the distinction between deliberate practice and deep work. They can seem to be the same thing and there is a lot of overlap, however there are some important differences. I consider deep work to be related to learning new material or working on an existing project with extreme focus. Examples of these include:</p><ul><li>Building a side project.</li><li>Reading up on a new subject and organizing your understanding (like Ruby in the 101 course).</li><li>Writing a blog post.</li><li>Reviewing some material you may have forgotten.</li></ul><p>Now, deliberate practice does incorporate deep work in requiring focus and lack of distractions. But the goal of deliberate practice is to improve an existing skill or to take your current understanding of material to another level. Examples include:</p><ul><li>Practicing concepts to improve on through small projects.</li><li>Solving coding problems that are harder than those you’ve previously solved.</li><li>Improving your ability to explain a difficult/complex concept (like prototypical inheritance in JavaScript)</li><li>Practice system design and algorithms in preparation for an interview.</li></ul><p>Try to implement both deep work and deliberate practice into your daily studies and see for yourself how a big difference they can make.</p><p><strong>The Feynman Method</strong></p><p>This last technique is one of my favorites and has shown up in quite a few articles. It’s a method popularized by Richard Feynman, a Nobel Prize winning physicist who is widely regarded as one of the greatest teachers for explaining complex ideas in simple terms. One of his most famous quotes is how he would explain the concept of atoms:</p><p><em>If, in some cataclysm, all of scientific knowledge were to be destroyed, and only one sentence passed on to the next generations of creatures, what statement would contain the most information in the fewest words? I believe it is the atomic hypothesis (or the atomic fact, or whatever you wish to call it) </em><strong><em>that all things are made of atoms — little particles that move around in perpetual motion, attracting each other when they are a little distance apart, but repelling upon being squeezed into one another</em></strong><em>. In that one sentence, you will see, there is an enormous amount of information about the world, if just a little imagination and thinking are applied. — Richard Feynman</em></p><p>During his graduate school days, Richard Feynman would take a brand new notebook and title it “Things I Don’t Know”. In this notebook, we would identify the gaps in his knowledge on a subject and dissect each detail until he had formed a complete understanding of the material. His process was actually quite simple:</p><ol><li>Identify the subject and write out everything you know about the subject. Do this without looking at any notes or resources, but instead recalling your subject knowledge from memory.</li><li>Explain the subject to someone who wouldn’t know anything about the subject. With this step, you are forced to use simple terms and focus on brevity.</li><li>Identify any gaps in your explanation, whether in your difficulty explaining a piece of the subject or questions from your audience that you couldn’t easily or simply answer. This is where the true learning begins.</li><li>Return to learning the gaps you discovered. Organize and simplify your explanation into a narrative that’s easy to convey.</li></ol><p>The power of this technique comes from the recall of information completely from memory (similar to spaced repetition) and the cycle of learning a subject, refining your understanding, trying to make it understandable to someone else, and identifying what you still need to improve on. Our brains are exceptionally good at making us believe that we are more fluent with a subject than we actually are (known as the <em>illusion of fluency</em>) and this technique makes it brutally clear how fluent you actually are on a subject.</p><p>Now this likely sounds like a lot of work, and it can be if you use it for every single concept in a larger subject area. So I would recommend that you pick a broad subject (like the fundamentals of Ruby or how HTTP works), and as you write out the details and follow the process you’ll naturally find the gaps to focus on. And of course, this technique is best implemented using deep work!</p><p>I hope that you try these techniques out and find them as useful as I have. Learning how to learn can be a rewarding and enlightening journey, and I highly recommend that you explore a range of techniques to find what works for you. If you have any tips or tricks that I didn’t cover or want to share your experiences with the ones that I have shared, please leave a comment. Thanks for reading!</p><h4>Book List</h4><p>Deep Work — Cal Newport</p><p>Mastery — Robert Greene</p><p>The Art of Learning — Josh Waitzkin</p><p>The 5 Elements of Effective Thinking— Burger &amp; Starbird</p><p>Mindset — Carol Dweck</p><p>Learning How to Learn — Dr. Barbara Oakley (Coursera)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=490a91d00584" width="1" height="1" alt=""><hr><p><a href="https://medium.com/launch-school/elevate-your-learning-490a91d00584">Elevate Your Learning</a> was originally published in <a href="https://medium.com/launch-school">Launch School</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Succeed on the 209 Assessment]]></title>
            <link>https://medium.com/launch-school/how-to-succeed-on-the-209-assessment-899a066dd8f7?source=rss-54c5cb7f84d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/899a066dd8f7</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[how-to-study]]></category>
            <category><![CDATA[launch-school]]></category>
            <dc:creator><![CDATA[Julius Zerwick]]></dc:creator>
            <pubDate>Sun, 08 Apr 2018 01:10:30 GMT</pubDate>
            <atom:updated>2018-04-09T10:17:12.110Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve just completed the 209 Assessment and wanted to reflect on my experience in studying for and completing it. Thus far, this assessment was the hardest one for me and I solidified an incredible amount of HTML &amp; CSS material in my brain for the assessment. In this post, I want to go over my thoughts on the course, assessment, and what I think is the best study plan for it.</p><p><em>Caveat: I completed this assessment after finishing the 201 course, which has since been replaced by 202. While there are differences in the content between the two courses, there is still a lot of overlap and I believe that this post will still be relevant and useful for students taking the assessment.</em></p><p><strong>Reflecting on the Course</strong></p><p>Overall, this course hit me like a ton of bricks and I struggled a fair bit in learning all the material. I personally found all of the back-end courses to be more suited to my prior knowledge of programming and easier for me to succeed in.</p><p>This was due to my past experience in both Python and Ruby prior to Launch School from college and online resources, along with being comfortable in the logical process of solving the back-end problems. In comparison, the topics and projects in this course were more difficult for me to complete and feel confident in since there are so many different ways to accomplish the same design in HTML &amp; CSS.</p><p>With each project, I felt like I was given a blank canvas and a bunch of new, weird art supplies to complete a portrait, and I had little confidence in myself to properly lay everything out and style accordingly. I found myself griping over each little detail that I missed or how to know what was <em>just the right amount</em> of padding to give an element. However, with each struggle, I gradually learned how each piece came together throughout the course.</p><p>I believe it is vital to take each lesson slowly so as to properly absorb the huge amount of information covered. You need to get a feel for how each element and style works on its own and in conjunction with each other so that you can understand the “why” when something breaks and how to fix it. Drill the concepts into your mind with the practice problems and small projects (examples offered below) in order to stay on top of all the topics.</p><p>I encourage everyone to work each project in the course a second time without looking at the completed project code. Add each line of code one at a time to take in and recognize the visual effect on the project. Over time, this will help you get a feel for how things should look and you’ll more easily be able to know how to adjust as you build each project. In fact, you may find that over time the process actually becomes more logical as you grow to understand how each element and style interplays with each other and can then exactly pinpoint what creates the issue you’re facing.</p><p><strong>My Impressions of the Assessment</strong></p><p>If I can emphasize one thing upon you regarding the assessment, it’s to not take it lightly! The project will require nearly everything from the course in one way or another. You’ll need to weigh the pros and cons regarding what HTML structures you should use to create the project and consider how it will affect your overall styling.</p><p>You’re given 48 hours to complete the project and it’s essential that you commit as much of that time as you can to work on it. By my estimate, I spent roughly 11–12 hours on the project from start to finish, and could easily have spent more.</p><p>Don’t let the seemingly generous time allotment fool you! This project is also a test of your time management, including your ability to gauge how long each requirement will take to complete and how much respect you give to the time needed to design and troubleshoot each feature. I urge you to only start this assessment when you can commit two full days to it like a weekend.</p><p>If you are studying at Launch School part-time and have other obligations that prevent you from committing two entire days for the project, then it’s absolutely critical that you relentlessly practice the concepts until you have them down cold. Then when you do start the project, you won’t need to look over the course material as much to troubleshoot and overcome any issues.</p><p>Amazingly, I found the assessment to be as much of a learning experience as a test of my skills and knowledge, which was also expressed by fellow student Tommy Caruso in an excellent discussion post under “Start Assessment 209” that I highly encourage you to check out. A lot of the material that is covered in the course truly sunk-in and synthesized when I had to figure out how to make the project’s various features and design work together.</p><p>Topics that I was shaky on became solidly ingrained after this trial by fire experience and I want you to know that it’s ok if you have to re-visit some topics while working on the project. Manage your time well, give each requirement it’s due time plus some, and you’ll make it through!</p><p><strong>My Recommendations</strong></p><p>In preparing for the assessment, I reviewed nearly all of the course material and redid all of the course projects a third time over. However, this process gave diminishing returns as I felt more accustomed to solving each project in the same way as shown in the course, and re-reading the material doesn’t truly help concepts sink-in. Beyond the second run-through of the projects, I didn’t gain much from re-working them.</p><p>A better approach I found was to complete a series of small projects in which the goal is to cement specific concepts in your brain with each project. This will force you to think deeply about how to complete something new and will require you to review material as you struggle, thus forming deeper connections on when to use certain topics and why they work the way they do.</p><p>This is what <strong>mastery-based learning </strong>is all about! Pick a project that pinpoints an area that you’re struggling with. Work on it until you hit a snag, then look up the relevant readings/practice problems to figure out a solution. Rinse and repeat until you’ve got a completed project and with a deeper knowledge of the material to boot.</p><p>It’s an important skill to be able to create our own practice for the topics we struggle on the most. Re-working past problems has diminishing returns and we must find new ways to stimulate our brain and maintain our edge.</p><p>Here is a list of projects I recommend you complete prior to starting the assessment:</p><ul><li>Create a web page that features several columns/rows of varying sizes and arrangements on the page. Review using floats, liquid &amp; fluid layout, CSS positioning, and media queries.</li><li>Create a web page with several icons/images that you can click on, which causes the icon/image to pop-up in the center of the page. The pop-up should be a larger size, and a dark background should appear behind it (hint: review opacity). Toy with changing where the pop-up appears on the screen.</li><li>Create a web page with content in several different containers (divs, articles, sections, etc.) and attempt to target different elements using complex CSS selectors.</li><li>Create a web page that has multiple forms to be completed by the user. Practice spacing and positioning all the form elements evenly, then change have some take up more space than others. Incorporate liquid &amp; fluid layouts.</li><li>Create a web page that uses tables to display the inventory of a store.</li><li>Create a web page that displays rows of content. Attempt to fill each row with 3–4 elements of various types (paragraphs, spans, images, inputs, labels, etc.). Style the elements to be evenly spaced in the row, then change them to be unevenly spaced (one can take up a fourth of the row, another half of the row, etc.).</li><li>Take any of the above projects and add media queries for the following breakpoints: 1080px, 768px, 480px.</li></ul><p>If you can complete all of these projects and understand all the concepts, then I think you’ll do very well on the assessment.</p><p><strong>Onward &amp; Upward</strong></p><p>I hope that this post has been helpful to everyone preparing to take the 209 assessment. It was certainly a challenging and rewarding experience for me and I look forward to studying the next course. What do you think of the HTML &amp; CSS course? How are you preparing for the 209 assessment? If you could offer any ideas for projects to practice the course topics, what would they be? Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=899a066dd8f7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/launch-school/how-to-succeed-on-the-209-assessment-899a066dd8f7">How to Succeed on the 209 Assessment</a> was originally published in <a href="https://medium.com/launch-school">Launch School</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why You Need an Interview Script]]></title>
            <link>https://medium.com/launch-school/why-you-need-an-interview-script-b86e18d0200a?source=rss-54c5cb7f84d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b86e18d0200a</guid>
            <category><![CDATA[how-to-study]]></category>
            <category><![CDATA[launch-school]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[interview-tips]]></category>
            <dc:creator><![CDATA[Julius Zerwick]]></dc:creator>
            <pubDate>Tue, 27 Mar 2018 15:17:24 GMT</pubDate>
            <atom:updated>2018-10-29T02:27:47.333Z</atom:updated>
            <content:encoded><![CDATA[<p>There are few things as anxiety-inducing as being interviewed for a job or as an assessment over coursework. It goes beyond merely stressful and creates a host of physical reactions: sweaty palms, shaky legs, labored breathing, a queasy stomach, and much more. All while your performance will ultimately determine your potential grades, salary, and career opportunities.</p><p>It’s no wonder that our ability to solve problems and answer technical questions degrades substantially under these conditions! And yet, many people brush off these concerns and hold onto an illusion of superior competence while under trial by fire. With so much depending on our ability to perform under stress, we should be smart about setting ourselves up for success and create a process to reduce this mental degradation while under pressure to perform.</p><p>That is why you need an interview script. Having a prepared script to follow will help you get into the flow of solving a problem before your anxiety can make you freeze and sink your performance. To illustrate its effectiveness, I’ll take you through a coding challenge using an interview script that I’ve created for myself and has helped me succeed in my assessments at Launch School.</p><h4><strong>Step 1: Read the problem and load it into your brain</strong></h4><p>First and foremost, you need to slowly read the problem and start processing it so that you can understand what you are being asked to solve. Start by writing out the problem’s main points in your own words.</p><p>Here is our code challenge:</p><pre><strong><em>Write a method that takes a string argument and returns a new string that contains the value of the original string with all consecutive duplicate characters collapsed into a single character.</em></strong></pre><p>Now, your first thought after reading may range from “This looks so easy!” to “Where do I even begin?”. Believe me, if you think this problem will be no sweat during an interview, that is the illusion of competence speaking to you. Every problem will seem more difficult when you are under the interview spotlight and can feel the gaze of your interviewer boring into you. Even problems that you may have handled with ease in the comfort of your home will suddenly morph into frightening monsters while under pressure.</p><p>Let’s take the prompt apart and write it out into something simpler to read:</p><pre><strong><em>- You are given a string argument for a method.<br>- This string may contain consecutive duplicate characters.<br>- Write a method that will take this string argument and return a new string.<br>- This return value will have all consecutive duplicate characters collapsed into a single character.</em></strong></pre><p>Include some examples of string arguments and the expected return values to illustrate what you want your solution to achieve.</p><pre><strong><em>Input: ‘bbbbbbbbb’ → Output: ‘b’<br>Input: ‘wwooonndeerrfull woorrlldd’ → Output: ‘wonderful world’</em></strong></pre><p>Great! This is more manageable and captures the main points, while also showing the interviewer how you can break down a problem into understandable parts. This will help to anchor you during the interview and serve as a reference while you craft your solution. The key is small victories along the way that demonstrate your skills and help you progress through the challenge while maintaining your confidence and flow. Breaking the challenge into smaller, manageable pieces is the first victory.</p><h4><strong>Step 2: Write out your approach in a step-by-step process.</strong></h4><p>Our next step will be to carefully layout our process for creating the solution in a step-by-step process. Doing so will allow you to focus on each individual step one at a time, while also making it easier to see the flow of the solution. Additionally, once you’ve solved the problem and receive some questions regarding refactoring or extra features, you can more easily see where in the flow to make your changes.</p><p>Here is my step-by-step process template:</p><pre><strong><em>Approach:<br>(1)<br>(2)<br>(3)<br>…</em></strong></pre><p>Using this template, I write out my high-level approach to solving the problem and then list each step in the solution’s execution. Here is my completed template for this challenge:</p><pre><strong><em>Approach: Use a loop within the method to check each character in the string. In this loop, we will check whether the character is equal to the next character. If it’s a duplicate, we will skip it. If it is not, then we will add it to a new string. At the end of the method, we will return the new string.</em></strong></pre><pre><strong><em>(1) Write a method definition that takes a string argument.</em></strong></pre><pre><strong><em>(2) Initialize a local variable assigned to a blank string.</em></strong></pre><pre><strong><em>(3) Initialize a local variable called index assigned to 0 to track which character we are checking in the loop.</em></strong></pre><pre><strong><em>(4) Create a loop that starts at index = 0 and repeats until index = string[-1].</em></strong></pre><pre><strong><em>(5) For each loop execution, check if the current character matches the following character.</em></strong></pre><pre><strong><em>  (i) If true, increment the index and start the next loop execution.</em></strong></pre><pre><strong><em>  (ii) If false, add the current character to the local string variable.</em></strong></pre><pre><strong><em>(6) Once the loop is complete, return the local string variable containing the string of distinct characters.</em></strong></pre><p>Phew! That may seem like a lot of writing, but it will make crafting the actual solution much faster and it will help you to answer any curveballs the interviewer may throw at you later. Another victory achieved!</p><h4><strong>Step 3: If no tests are provided, write some out with your expected output.</strong></h4><p>Remember, good engineers test their code! Your interviewer may provide you with some tests, but be prepared to write some yourself. Here are some tests that I would write for this problem:</p><pre><strong>collapse(‘bbbbbbbbb’) == ‘b’<br>collapse(‘wwooonndeerrfull woorrlldd’) == ‘wonderful world’<br>collapse(‘222xyzxyzyx’) == ‘2xyzxyzyx’<br>collapse(‘Q’) == ‘Q’<br>collapse(‘AAbbCC’) == ‘AbC’<br>collapse(‘’) == ‘’</strong></pre><p>Do not take this step for granted! It is a vital component in the process to show your value as a strong applicant. An engineer that thoroughly and consistently tests their code will stand out among other applicants, and the best places to work highly value good testing practices.</p><h4><strong>Step 4: Layout your rough draft of the problem with pseudocode.</strong></h4><p>At this time, we can start writing out the skeleton of our solution. Start with the basic method definition, and then write out the steps from your approach in your solution. Note: you should prioritize completing a working solution, even if it is a brute force solution with some redundancy. Once it’s finished, you can and should refactor your code.</p><pre><strong>def collapse(string)<br>  INITIALIZE A NEW EMPTY STRING VARIABLE collapsed_string<br>  INITIALIZE index AT ZERO.<br>  while index &lt;= string[-1]<br>    START WITH FIRST CHARACTER AND EXAMINE NEXT CHARACTER.<br>    if THEY ARE THE SAME,<br>      INCREMENT index BY 1<br>      SKIP TO NEXT CHARACTER FOR LOOP.<br>    else<br>      ADD CURRENT CHARACTER TO NEW STRING VARIABLE.    <br>    end<br>    INCREMENT index BY 1<br>  end<br>  RETURN collapsed_string<br>end</strong></pre><p>Now, this step may seem extraneous considering that you already wrote your steps out in the template above. However, using pseudocode to outline your solution is like writing your first draft of a paper. It provides the skeleton that you’ll flesh out moving forward, and there is already some code written. Remember, small victories along the way will keep you in the flow and prevent your confidence from wavering under the spotlight.</p><h4><strong>Step 5: Rewrite solution in actual code.</strong></h4><p>Now take each line of pseudocode and replace it with actual, functioning code.</p><pre><strong>def collapse(string)<br>  collapsed_string = ‘’<br>  index = 0<br>  while index &lt;= string.length<br>    if string[index] == string[index + 1]<br>      index += 1<br>      next<br>    else<br>      collapsed_string &lt;&lt; string[index]<br>    end<br>    index += 1<br>  end<br>  collapsed_string<br>end</strong></pre><p>No sweat right? At this point, you have been running a consistent train of thought on how to solve this challenge and avoided freezing up.</p><h4><strong>Step 6: Test your code.</strong></h4><p>Now it’s time to test! If given the chance to use a computer, run your tests and see if they all pass. If you’re on a whiteboard, go through some tests by hand to make sure that your solution executes as expected.</p><p>If you encounter any issues, this is a good thing! You’ve shown that you are willing to check your code and can handle fixing bugs. Remember: very rarely does ANY code work on the first run and it’s completely normal to undergo a few revisions before a successful run. It’s more important to show that you are comfortable with the process of creating, testing, and refactoring your code to completion, and will do so with any code you work on.</p><h4><strong>Step 7: Refactor your code.</strong></h4><p>So now you’ve gotten all your tests to pass and you’ve cleared the challenge. Awesome job! But it doesn’t stop there, and you will likely be asked by your interviewer if you can refactor your code to improve it. Hopefully, the previous steps have given you an in-depth understanding of the problem and your own solution to easily identify areas of improvement.</p><p>Let’s go through our code and look for areas to refactor:</p><pre><strong>def collapse(string)<br>  collapsed_string = ‘’<br>  index = 0<br>  while index &lt;= string.length<br>    # condense conditional into a single line using “unless”<br>    if string[index] == string[index + 1]<br>      index += 1<br>      next<br>    else<br>      collapsed_string &lt;&lt; string[index]<br>    end<br>    # remove redundant “index += 1” line<br>    index += 1<br>  end<br>  collapsed_string<br>end</strong></pre><p>By condensing the if else conditional into one line with the ‘unless’ keyword and removing the redundant ‘index += 1’ line, we can shorten our solution by 6 lines!</p><pre><strong>def collapse(string)<br>  collapsed_string = ‘’<br>  index = 0<br>  while index &lt;= string.length<br>    collapsed_string &lt;&lt; string[index] unless string[index] ==<br>    string[index + 1]<br>    index += 1<br>  end<br>  collapsed_string<br>end</strong></pre><p>And there you go! We now have a more compact and readable solution with just a bit of refactoring.</p><h4><strong>Step 8: Handle any curveballs.</strong></h4><p>It’s no secret that once you’ve solved and refactored the initial problem, your interviewers will likely ask how you would modify it to handle a new scenario. This is another reason why we’ve taken such a detailed approach to solving the problem, as you’ll be much more comfortable with the conditions of the problem and can adjust to these curveballs.</p><pre><strong><em>Potential Curveballs:</em></strong></pre><pre><strong><em>(1) What about a string that’s a mix of upper &amp; lower case letter? Ex: ‘AaABBb’</em></strong></pre><pre><strong><em>(2) What about an invalid input, like integer values? Ex: 1234</em></strong></pre><pre><strong><em>(3) What about a mix of string characters and integer values? Ex: ‘AbC’45’deF’</em></strong></pre><p>These can be addressed either through refactoring your solution or using exceptions to handle invalid input. I’ll leave these as an exercise for the readers to attempt for practice. By this point, I hope that my script has gotten you into the flow of solving this challenge and made you feel confident about handling these curveballs.</p><h3><strong>Practice and Improve the Script</strong></h3><p>Now that you have the script, you need to practice using it in order to reap the maximum benefit from it. Incorporate it into every coding problem you face, no matter how simple it may seem. While the steps laid out above may help you solve difficult problems, it’s main purpose is to anchor your thinking, maintain your flow and confidence, and fight the mental degradation during an interview or assessment.</p><p>The more problems that you complete using the script, the easier it’ll become to get started solving a problem while under the pressure to perform. In fact, I believe that it will help you stand out among other interviewees who don’t have a practiced script and end up floundering around a bit before making any progress on the problem. Every inch counts in your interview and against your competition, so make use of this script because I can assure you that there will be others who won’t.</p><p>Note that this is the script that has worked for me thus far, and I will improve upon it as time goes on. You should make your own modifications that suit your style, whether it’s creating your own step-by-step process template or how you initially identify the main points of the problem. Just make sure that you follow the overall process and methodology of the script, which is breaking down problems into smaller, digestible pieces that you can manage while under pressure and will earn you small victories along the way.</p><h3>Conclusion</h3><p>I hope that this script proves useful to you in your future interviews and assessments. If you have any additional points that I may have missed or a particular technique/step that you have found helpful in your own problem solving, please leave a comment below. I’m interested in hearing your thoughts and experiences and look forward to the discussion. Thank you for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b86e18d0200a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/launch-school/why-you-need-an-interview-script-b86e18d0200a">Why You Need an Interview Script</a> was originally published in <a href="https://medium.com/launch-school">Launch School</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Halfway There: Reflections After 9 Months with Launch School]]></title>
            <link>https://medium.com/launch-school/halfway-there-reflections-after-9-months-with-launch-school-485c91be7439?source=rss-54c5cb7f84d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/485c91be7439</guid>
            <category><![CDATA[codingbootcamp]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[launch-school]]></category>
            <category><![CDATA[how-to-study]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Julius Zerwick]]></dc:creator>
            <pubDate>Sun, 11 Feb 2018 22:05:21 GMT</pubDate>
            <atom:updated>2018-02-16T20:57:33.113Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nh409k__0Xg1cm753AYF-w.jpeg" /></figure><p>I’ve recently completed the Programming &amp; Back-End Development coursework at Launch School and wanted to take the time to pause and reflect on the experience, as well as consider the road ahead. The past 9 months at Launch School have been an incredible experience in my growth as a software engineer and student, and I think it’s important to reflect on the past to improve the future.</p><h3>The Difference in Launch School</h3><p>Right before I started studying at Launch School in April 2017, I had just completed a 6-month online boot camp in web development. The boot camp had seemed to offer a solid program on the surface with one-on-one mentorship, a diverse set of technologies to learn and a group project to highlight on our resumes. However, the majority of the 6 months was spent creating projects with Ruby on Rails after only 1–2 weeks of Ruby fundamentals and speed through JavaScript and databases in less than a month. By the end, I felt a clear discomfort in my skills when I couldn’t understand how these technologies worked beneath the surface and failed to fix a lot of bugs in my projects after some tinkering. In fact, I felt that my knowledge was so lacking that I couldn’t even put JavaScript and Rails on my resume.</p><p>This discomfort led me to reconsider applying for jobs as I didn’t feel like a strong candidate with a firm command of the fundamentals. And while the boot camp instructors stated that we would learn a lot more while on the job, I didn’t feel like a competitive candidate. And even if I was hired, I felt like I would be a weak team member who would play catch-up instead of learning other areas of software development for my job.</p><p>With these concerns, I found Launch School and decided to humble myself. I would disregard the feeling of sunken-cost (a common fallacy) from my 6-months spent with the boot camp and start over from the ground up with Launch School. And that has been one of the best decisions I’ve ever made as I’ve now learned an unbelievable amount about Ruby, OOP, SQL, and web development and feel incredibly more confident as a programmer.</p><p>The difference was crystal-clear after the 101 Programming Foundations course that broke Ruby down completely and elevated my abilities to problem solve with Ruby. I spent about 3 months finishing the 101 course and I can say that the 1–2 weeks of Ruby training from my boot camp was utterly insignificant and lacking. Launch School is simply on another level that actually trains its students to be strong programmers due to its mastery-based learning model.</p><h3>Point of Acceleration</h3><p>Fast forwarding to the start of this year, I was almost through the 180 SQL &amp; Relational Databases when Chris Lee posted about a Capstone Info Session webinar. This piqued my interest as I had been eyeing the Capstone Program since I found Launch School and was determined to get accepted into it from the start.</p><p>This desire was because I knew Capstone would be instrumental in molding me into the best software engineer that I could be for my job hunt and propel my career. And what really drew my attention was that the next Capstone cohort would start on May 14th. After some digging around, I found that the applications for Capstone were usually due about a month before the start date, so April 1st.</p><p>This lit a fire in me as I wanted to be in that cohort. I had already been studying for 9 months and felt confident in my abilities as a student to reach the April 16th deadline, especially since I had studied HTML &amp; CSS before Launch School. And so I decided that I would increase my daily study hours and do my best to complete the entire Front-End Development coursework within 3 months, which gave me about 2.8 weeks to finish each course and assessment.</p><p>And that is a prime example of hubris and allowing emotion to cloud judgment.</p><h3>Avoiding the Inevitable Crash</h3><p>It didn’t take long for me to seriously question my new plan as the 201 HTML &amp; CSS course revealed itself to be a monster. Just like how the 101 course showed how weak my Ruby fundamentals were, the 201 course was quickly making it clear that I really didn’t know HTML &amp; CSS as deeply as I thought. The sheer amount of readings and content to learn was shocking and I began to doubt that I could absorb it all and show a mastery of the material while on my aggressive timeline.</p><p>At this point, I had to do something that has always been a bit painful but ultimately very beneficial for me: I had to detach myself from the situation and assess myself against the cold truth. I could not realistically expect myself to learn all of this material to the point of mastery in just 2.8 weeks, and then repeat this feat with the 210, 225, &amp; 230 courses. Additionally, I had to make a plan to refresh and maintain my knowledge of the Back-End coursework lest I become rusty in these skills for Capstone.</p><p>The truth was that I wanted so badly to be in Capstone and start my job hunt that I was making decisions which would harm my mastery of the courses and abilities as a programmer. Even if I could go through all the coursework within 2 weeks, would I do well-enough on the assessments? By putting my self-imposed deadline before mastery-based learning, I could end up bombing an assessment and thus tank my standing as a candidate for Capstone. And if I solely focused on the Front-End for the next 3 months and didn’t review the Back-End, would I end up as a weak Capstone student?</p><p>These questions felt oddly similar to the ones I asked myself after my boot camp experience and showed that my judgment had been clouded.</p><h3>My Current Path</h3><p>In the end, I made the decision to slow down and focus on the here and now, which is learning the current course as best as I can for as long as it needs to take. This approach has been the reason that I’ve succeeded on the assessments thus far and if the method isn’t broken then I shouldn’t change it. Additionally, I need to build an effective review method for the material of the previous courses to remain a strong back-end programmer. I need to trust the process that has been successful so far and move forward with it.</p><p>I chose Launch School to rebuild my abilities and become a strong software engineer, and I can’t allow myself to become impatient. I know that a brighter future and career lies ahead at the end of the road so long as stay consistent and humble in my learning. My eye is now on applying for the Capstone cohort in the fall of this year and I can already tell that this choice feels correct.</p><p>I want to wish everyone studying at Launch School good luck on their courses and I hope you enjoyed reading this reflection. Remember that as much as we all want to improve quickly, mastery does not accept deadlines. It in fact breaks them as useless constructs. Stay strong and get after those courses!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=485c91be7439" width="1" height="1" alt=""><hr><p><a href="https://medium.com/launch-school/halfway-there-reflections-after-9-months-with-launch-school-485c91be7439">Halfway There: Reflections After 9 Months with Launch School</a> was originally published in <a href="https://medium.com/launch-school">Launch School</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>