<?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 Tim Park on Medium]]></title>
        <description><![CDATA[Stories by Tim Park on Medium]]></description>
        <link>https://medium.com/@thetimothyp?source=rss-d1d670db6a46------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*rr20VCcdl0RmvWPg.</url>
            <title>Stories by Tim Park on Medium</title>
            <link>https://medium.com/@thetimothyp?source=rss-d1d670db6a46------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 23:54:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thetimothyp/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[My first step into the world of Software Development — and what you can learn from it.]]></title>
            <link>https://medium.com/free-code-camp/my-first-steps-into-the-world-of-software-development-and-what-they-taught-me-6ee748cffb8f?source=rss-d1d670db6a46------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ee748cffb8f</guid>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Tim Park]]></dc:creator>
            <pubDate>Thu, 04 Jan 2018 10:58:41 GMT</pubDate>
            <atom:updated>2018-01-05T09:26:39.313Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xNwbQ2Ec0xoq_DMPbxR5yw.png" /><figcaption>*Nervous laugh* (<a href="https://www.youtube.com/watch?v=fZ_JOBCLF-I">Source</a>)</figcaption></figure><p>As a budding student of computer science, there’s a disconnect between what you learn in class and what you see in the real world. You learn all there is to know about loops of every variety—for, while, do while. You can write a command line based tic-tac-toe game like it’s nobody’s business. And you write so much fill-in-the-blank x86 assembly that it makes your head spin.</p><p>But you haven’t the slightest clue how something like Facebook works. Or Reddit. Or YouTube. You don’t even have an inkling of where to begin.<strong><em> </em></strong>When you Google “companies that use python,” since Python is the only language you know, you find people saying things like “<a href="https://www.quora.com/What-top-tier-companies-use-Python">Reddit…uses python for their backend</a>.” Backend? What does that even <em>mean</em>?</p><p>There’s this giant gap in your knowledge between writing tic-tac-toe for the command line and building a “real” application, and nobody is telling you how to fill it in. Even though you’ve learned all about how to <em>think</em> logically, you have no idea how to <em>apply</em> what you’ve learned in order to build the things you want to build.</p><p>Here’s the thing: it takes <strong>initiative</strong> to get to where you want to be. You won’t always have professors giving you templates and boilerplate for all your projects, leaving you to fill in the blanks. You won’t always have a lesson plan telling you “This is what you need to learn next.”</p><h4>Takeaway #1:</h4><p><strong>Nobody has more influence over your personal development than you. </strong>It’s up to <em>you</em> to decide what you want to learn, without someone spoon-feeding you the next step every step of the way. This self-directed learning, <a href="https://danluu.com/learning-to-program/">what Dan Luu might describe as a meta-skill</a>, is one of the most important skills you’ll pick up in your journey towards becoming a software developer.</p><p>Luckily, these days we have Google to help out. “How to build a website using python,” you search. You stumble across this <a href="http://flask.pocoo.org/docs/0.12/">nifty little web framework</a> and decide to give it a shot—not that you actually know what a framework is. You try reading the documentation from the beginning, don’t understand any of it (“database abstraction layer?”), and skip ahead to the <a href="http://flask.pocoo.org/docs/0.12/installation/">installation</a> step.</p><p>Finally, some actionable steps to follow! You copy the commands into your terminal. There’s something about something called pip, and virtualenv, whatever those are. You take a minute to look those up, just so you have an idea of what you’re doing to your machine.</p><h4>Takeaway #2:</h4><p><strong>We learn by understanding, not by mindlessly following instructions.</strong> Get used to learning instead of giving up when you don’t understand something, and you’ll see that seemingly impossible tasks are really just greater opportunities to grow—it’s only a question of how long it takes.</p><p>Okay, looks like pip is a utility to install packages so you can import them, just like we import the built-in math package. Virtualenv seems like a way to isolate package installations to a specific project. You still don’t <em>fully</em> understand any of the commands besides mkdir and cd, but you‘re not totally clueless either. Time to move on to the <a href="http://flask.pocoo.org/docs/0.12/quickstart/">quick start guide</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VTSusSgKZIr6tZDPl4n3Rg.png" /><figcaption>Just follow along and try to keep up. (<a href="https://unsplash.com/photos/lRssALOk1fU">Source</a>)</figcaption></figure><p>You follow the initial instructions, and there’s a burst of elation when you run your program and see “Hello, world” in your browser for the first time. You think to yourself, now <em>this</em> is what I’m talking about! No more boring old command line programs for me! It’s a small step, to be sure, but that’s <em>your</em> <em>code</em> in the browser, and that’s significant.</p><p>You continue, but start running into a lot of concepts that you don’t fully understand. Routes? HTTP? GET? POST? And what are rendering templates? Some of these terms seem vaguely familiar, but you don’t actually know what they mean, so you stop along the way to look them up. Just like you learned about pip and virtualenv, you start to assemble a fuzzy picture of how this application is working.</p><h4>Takeaway #3:</h4><p>Learning takes practice. Just like any other skill, it needs to be honed. And just like any other <strong>practiced</strong> skill, it can become a habit. Seize every opportunity you have to learn. Remember: success begets success. <strong>Make learning a habit, and not only will your personal growth skyrocket, but your desire to learn will grow as well.</strong></p><p>You can use templates to display content like you would with any other HTML/CSS page, but the content is dynamic. You can control what content is displayed at different URLs by defining routes. You can even fetch content from other websites to use in your own application!</p><p>As you get more and more comfortable, you start to feel a degree of control and pride in your independent learning that you’ve never felt while working on any of your class projects. You feel empowered. Who even needs school, anyway?</p><p>As you gain confidence, the guide starts to feel a little…basic. It is, after all, a quick start guide. I could do something cooler than this, you think.</p><p>So you strike out on your own. You set up your project the same way you did before, with pip and virtualenv, because that’s the only way you know how to set up a project. You know how to set up the templates. You know how to set up the routes, the HTTP requests, the GETs and the POSTs. You might even dare to use a third party API and practice reading some more documentation. You still don’t understand everything, but you’re learning, bit by bit.</p><p>And finally, you build your very first independent side project. Not the result of a tutorial that hundreds of budding developers before you have followed. Not a class assignment that thousands of students before you have done. A real, tangible, honest-to-goodness application that would not exist had you not built it. <strong>And that’s an amazing feeling.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Aa2xWQ-1cROTglJ6DPygdg.png" /><figcaption>You are a master builder. (<a href="https://www.warnerbros.com/lego-movie">Source</a>)</figcaption></figure><p>So what’s next? Now that you’ve built an application, how do you put it online so everyone can use it? What really is a “back end?” A front end?</p><p>Here’s the great thing about fostering a desire to learn: there’s always more. It’s like an amazing television series that you can never get enough of—<strong>and it never ends.</strong> There’s no such thing as learning <em>too much</em>. Every discipline in software development is an entire new world to dive into, and the more you learn, the more worlds are opened up to you.</p><p>At some point, you realize that there is no single canonical path to being a “real” software developer. There’s not enough time to master every single thing. Everyone’s path to success is totally unique. <strong>It’s entirely up to you to forge a path to the destination you want to reach.</strong></p><p>This was the story of my own first step into the world of software development. If you want to see the very first side project that I ever built, <a href="https://github.com/thetimothyp/Where2Eat">you can check it out here</a>.</p><p>And if you feel like sharing your own, feel free to post a link in a response! I’m always curious to see what kind of code people start out writing.</p><h4>If you like what you read, <a href="https://medium.com/@thetimothyp">there’s more where that came from</a>!</h4><p>As a guy in the early stages of his tech career, I write about — you guessed it — the early stages of a tech career.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ee748cffb8f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/free-code-camp/my-first-steps-into-the-world-of-software-development-and-what-they-taught-me-6ee748cffb8f">My first step into the world of Software Development — and what you can learn from it.</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[How I got my first developer job with no internships straight out of college]]></title>
            <link>https://medium.com/free-code-camp/how-i-got-my-first-developer-job-with-no-internships-straight-out-of-college-814d0eea1e4c?source=rss-d1d670db6a46------2</link>
            <guid isPermaLink="false">https://medium.com/p/814d0eea1e4c</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Tim Park]]></dc:creator>
            <pubDate>Sat, 16 Dec 2017 16:05:17 GMT</pubDate>
            <atom:updated>2018-01-05T00:30:35.018Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>5 key elements that will make all the difference in your job search</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R1pZ4yoGVqTCI2BM5s8Oow.png" /><figcaption>My many suitors.</figcaption></figure><h3>Getting a job out of school is hard.</h3><p>Especially when it seems like every other fresh graduate has been interning at Google or Facebook or Amazon (or all three) since sophomore year. Believe me, I know. When I started my job hunt at the beginning of this year, I sent out <strong>93</strong> job applications, <strong>2</strong> of which resulted in full time job offers. <strong>That’s about a 2% conversion rate from applications to full time offers.</strong></p><p>A little background…</p><p>I graduated from a mid-tier school with mid-tier grades and a grand total of zero internships under my belt. I got my A’s, my B’s, my C’s, and a couple D’s (apologies to my parents) — strictly in the middle of the pack.</p><p>The point is, <strong>I didn’t stand out.</strong> So why would anyone hire me in <a href="https://www.glassdoor.com/blog/20-in-demand-jobs-with-the-most-competition/">one of the most competitive job markets out there</a>? There are literally thousands of more qualified candidates companies could choose from.</p><p>Looking back, there are <strong>5 key elements </strong>that contributed to my eventual employment. I’ve tried to distill what I learned into fairly generic attributes. They are applicable whether you’re a fresh CS grad like me or an <a href="https://www.themuse.com/advice/how-i-went-from-a-career-in-education-to-an-employed-software-engineer-in-4-months">elementary school teacher looking to switch careers</a>.</p><p>So, without further ado, here are <strong>5 Key Components to Landing your First Tech Job (No Internship Edition)</strong>.</p><h3>Element #1: Persistence</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*WukC8UNQ2C3m4RtBxCbgZQ.png" /><figcaption><a href="https://imgur.com/gallery/xByII">Imgur</a></figcaption></figure><p>As mentioned earlier, I got 2 job offers out of 93 applications. This is about a 2% conversion rate (or 46 rejections per offer). That is to say, unless you’re an engineering god, <strong>you will face a lot of rejection</strong>. It will get discouraging.</p><p>Just remember, that there are so many reasons that a company might reject a candidate. That is beyond your control. For example, reduced headcount, internal re-organisation.</p><p>So <strong>don’t take it personally</strong> and keep on trucking. Who knows? Maybe the next application you send is the one that gets you an offer. <strong>Don’t make the mistake of giving up early and missing out on what might be your next job.</strong></p><h3>Element #2: Diligence</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*8PScCRxFwGQIxWOUcjgHgg.gif" /><figcaption>Courtesy of <a href="https://gph.is/2fXupOE">GIPHY</a></figcaption></figure><h4>Practice, practice, practice.</h4><p>Technical interviews are simple — you either meet the hiring bar, or you don’t. That means <strong>you have to be ready for the interviews that come your way</strong>. For me, that meant 2–4 hours of interview prep a day for the 3 months I was recruiting.</p><p>You may not have that kind of time, but the point is, make sure that you are prepared to the best of your ability for the opportunities you’re given — because if your job application looks anything like mine, then those opportunities are going to be few and far between.</p><p>Interview prep is its own beast, so I won’t go in depth on what my study regimen was in this article, but here are a few resources that I found useful when studying:</p><h4>Algorithms and Data Structures</h4><ul><li>Steven Skiena’s <a href="https://www.amazon.com/Algorithm-Design-Manual-Steven-Skiena/dp/1849967202">Algorithm Design Manual</a> (<a href="https://edisciplinas.usp.br/pluginfile.php/1995283/mod_resource/content/1/Skiena.-.TheAlgorithmDesignManual.pdf">PDF</a>)</li><li>Steven Skiena’s <a href="https://www.youtube.com/playlist?list=PLOtl7M3yp-DV69F32zdK7YJcNXpTunF2b">Analysis of Algorithms lectures on YouTube</a></li></ul><h4>Practice Interview Questions</h4><ul><li><a href="https://leetcode.com/">Leetcode</a></li><li><a href="https://codefights.com/">CodeFights</a></li><li><a href="https://www.firecode.io/">Firecode.io</a></li></ul><h4>Basic Program Design</h4><ul><li>Peter Norvig’s <a href="https://www.udacity.com/course/design-of-computer-programs--cs212">Design of Computer Programs</a></li></ul><h3>Element #3: Resourcefulness</h3><h4>Use everything (and everyone) at your disposal.</h4><p>Use your school’s career portal to apply to small companies that will take your cheap, inexperienced labor, and build up your skills in a low risk environment. You will not be paid much. It will not be glamorous. But it’s something to put on your résumé and it’s one step closer to the job you want to end up at.</p><p>Full disclosure, this is <em>exactly</em> how I got my first development job during my last year of school. That was literally the only job I had on my résumé alongside a list of side projects when it came time to apply to the bigger tech companies.</p><p>Leverage your personal connections, if you have any. Ask your parents’ friends’ friends if they can forward your résumé to the right people in their companies. Ask that guy you met on the train. Ask that woman you met at that party. People love to help out, and it’s such a small ask that odds are no one is going to straight up reject your request to forward an email for you.</p><p>Everyone owes their success to someone, so don’t feel bad about asking for help. In fact, the people you’re asking probably got to where they are <em>because</em> they asked enough questions to get there. And when the time comes that people are coming to <em>you</em> for help, remember all the people who helped you get to where you are and make sure to pay it forward!</p><h3>Element #4: Soft Skills</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*tPeQiIYibHbz6hVY2GSHYQ.gif" /><figcaption>Courtesy of <a href="https://media.giphy.com/media/6crVJRXHV8UVy/giphy.gif">GIPHY</a></figcaption></figure><p>I like to think it was my scrappy, go-getter attitude and my magnificent engineering chops that charmed my interviewers and awed them into extending me an offer. It was not. Thankfully, you only need to be a decent human being with basic communication skills.</p><p>Are you receptive to criticism, or are you obstinately defensive? Are you able to articulate your thoughts clearly, or is your logic hard to follow? Are you a good teacher, or do you get impatient when someone lacks understanding? Ultimately, <em>are you someone I would want to work with</em>?</p><p>According to Forbes, a lack of soft skills can kill your chances of being hired, with a <a href="https://www.forbes.com/sites/lisaroepe/2017/08/18/why-soft-skills-will-help-you-get-the-job-and-then-promoted/#16e4daf154b8">whopping 75% of recruiting professionals cutting their interviews short because of insufficient soft skills</a>. So brush up on your soft skills, because they might even be what saves an otherwise terrible interview.</p><p>Case in point: I got one of my offers after one of my worst interviews ever, because they “liked my positive energy”. They said that on the phone when I got my offer. <strong>So be positive. It’ll get you a job.</strong></p><h3>Element #5: Luck</h3><p>This one actually isn’t that helpful. Sorry!</p><p>With no internships and a paltry list of hacked together pet projects on my résumé, what incentive was there for recruiters to reach out to me amidst the sea of ex-Google interns and Stanford grads? To be honest, not much.</p><p>When my résumé hit the recruiters’ desks (or inboxes), it basically boiled down to whether they were feeling generous enough to give me a chance to interview.</p><p>There’s not much you can do here, so don’t take rejections personally. Make sure to “please keep an eye out for any future opportunities.”</p><h3>The important thing to recognize is that some of the hiring process is entirely out of your control.</h3><p>Use that knowledge to motivate yourself to take full advantage of the things you <em>do</em> have control over.</p><p>Be <strong>persistent</strong> in your efforts to seek out every single potential opportunity. Be <strong>diligent</strong> in your preparations so that you are ready to crush the interviews that you <em>do</em> get. Be <strong>resourceful</strong> in maximizing the number of leads you have through your personal connections and career centers. And finally, hone your <strong>soft skills</strong> to the point where everyone you meet will want to work with you.</p><h3>There is no secret formula that you can follow that will get you hired.</h3><p>There’s no magic number of Leetcode questions to complete to get hired, no sequence of steps to follow to magically unlock a job offer. When you get rejected, <a href="https://www.google.com/search?q=technical+interviews+ineffective&amp;oq=technical+interviews+ineffective&amp;aqs=chrome..69i57.7438j0j7&amp;sourceid=chrome&amp;ie=UTF-8">don’t blame the interview process</a>. Don’t blame the engineers who interviewed you. <strong>You and I don’t get that luxury. </strong>Because at the end of the day, we’re just poor ex-students trying to get hired, and no amount of blame shifting will change that, no matter how broken and/or useless you might think the hiring process is.</p><h4>With every rejection, ask yourself:</h4><ul><li><strong>What</strong> areas did I do poorly in?</li><li><strong>Why</strong> did I do poorly in those areas?</li><li><strong>How</strong> can I improve those areas for next time?</li></ul><p>Identify your weaknesses and work hard to remedy them, because in the end, that’s really all it boils down to: a little bit of luck and a whole lot of hard work.</p><h4>If you like what you read, <a href="https://medium.com/@thetimothyp">there’s more where that came from</a>!</h4><p>As a guy in the early stages of his tech career, I write about—you guessed it—the early stages of a tech career.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=814d0eea1e4c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/free-code-camp/how-i-got-my-first-developer-job-with-no-internships-straight-out-of-college-814d0eea1e4c">How I got my first developer job with no internships straight out of college</a> was originally published in <a href="https://medium.com/free-code-camp">We’ve moved to freeCodeCamp.org/news</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>