<?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 Paul Kim on Medium]]></title>
        <description><![CDATA[Stories by Paul Kim on Medium]]></description>
        <link>https://medium.com/@pkayokay?source=rss-6cdcf5ae06f3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Paul Kim on Medium</title>
            <link>https://medium.com/@pkayokay?source=rss-6cdcf5ae06f3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 18:08:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pkayokay/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[Resources to Learn How to Code]]></title>
            <link>https://medium.com/@pkayokay/resources-for-learning-how-to-code-a59814d4d8d1?source=rss-6cdcf5ae06f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/a59814d4d8d1</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[computer-science]]></category>
            <dc:creator><![CDATA[Paul Kim]]></dc:creator>
            <pubDate>Thu, 26 Apr 2018 01:31:53 GMT</pubDate>
            <atom:updated>2022-11-21T20:18:26.596Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’re an aspiring developer and want to learn how to code. There are plenty of free resources out there. Here’s a short summary of my experience with a few.</p><p>(Free = F , Paid = P)</p><ol><li><a href="http://www.codecademy.com/"><strong>Codecademy</strong></a> (F, P) — the hardest thing about learning how to code is the syntax (set of rules for the language). Codecademy does a fabulous job at enforcing correct syntax and teaching logic. I repeated their HTML, CSS, JavaScript, and Ruby section 2–3 times to get used to writing code.</li><li><a href="http://www.freecodecamp.com/"><strong>FreeCodeCamp</strong></a> (F) — teaches you the basics, but does not hold your hand so much. It takes a lot of googling to figure out how to solve some of the problems on there. You follow a curriculum and build projects. They even connect you with a non-profit for you to get real-world experience. Most people actually never get to this point or even finish the curriculum because they usually land a job by then.</li><li><a href="http://www.udacity.com/"><strong>Udacity</strong></a> (F , P) — offers high quality courses taught by industry experts. A lot of the courses from their Nanodegree program are actually free. Various new topics: AI, AR, VR, Machine Learning, Flying Cars.</li><li><a href="http://www.lynda.com/"><strong>Lynda</strong></a> (P) — provides source files to work along-side of video tutorials. They have tracks for different skills which makes it easy to follow. Plus, you can add a Lynda certification to your LinkedIn profile after each course. There’s a way to get it for free for most states, if you have a library card you should be able to get a login and use it for free. It’s also free for students.</li><li><a href="http://www.teamtreehouse.com/"><strong>Treehouse</strong></a> (P) — explains things in detail, tracks for different types of development, all video. Love their CEO, Ryan Carson. He’s all about giving opportunities and providing a way to earn a good living without a college degree (or getting in debt).</li><li><a href="http://www.codewars.com/"><strong>CodeWars</strong></a> (F) — this is a great resource to really learn a programming language. It helps you apply the language to logical problems (and algorithms). It forces you to learn the methods of a language and its capabilities. Great for a whiteboard/coding interview.</li><li><a href="http://www.youtube.com/"><strong>YouTube</strong></a> (F) — there is a lot of old content on here I’ve found it useful to look up things when I don’t understand a concept. It’s good for computer science concepts that will not really change over time.</li></ol><p>These resources definitely do not replace official documentation, you’ll find that as you advance in your career you’ll grow out of these and just figure things out as you go!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a59814d4d8d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Pragmatic Approach to Landing Your First Developer Job]]></title>
            <link>https://medium.com/@pkayokay/a-pragmatic-approach-to-landing-your-first-developer-job-669cef612852?source=rss-6cdcf5ae06f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/669cef612852</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[career-advice]]></category>
            <dc:creator><![CDATA[Paul Kim]]></dc:creator>
            <pubDate>Sat, 18 Nov 2017 15:29:47 GMT</pubDate>
            <atom:updated>2022-11-19T02:56:30.529Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*evFxum5mqnHdXC_06DDtEQ.png" /></figure><p>A lot new developers are driven by fear, these are some of the excuses I’ve used and many others use:</p><ul><li>I’m not “ready” for the job.</li><li>I need to build more projects.</li><li>I’ll apply later once I “master” this [insert language here].</li></ul><h4>The truth is, it‘s not as difficult as many make it to be. It’s a matter of action, you need to be practical.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*XFHm0X7Op2WTKCULrIMaiw.png" /></figure><p>I spent many months wasting time googling questions like: “how to prepare for a developer interview”, “what to except at a technical interview”, “how to become a web developer”…I neglected the time I could have spent learning (and applying).</p><p>If many new developers are driven by fear and do not apply because they feel they are not “ready”, then why not be the small percentage that actually applies?</p><h3>Here are some practical steps to getting your foot in the door:</h3><h3>STEP 1:</h3><ol><li><strong>Resume</strong></li></ol><ul><li>Include relevant experience.</li><li>Tailor your resume to the role you are applying for.</li><li>Include hyperlinks to your Email, Github, LinkedIn, and Porfolio.</li><li>Do not name your resume “resume.pdf”. Add your name to it. “johnsmith_resume.pdf”.</li></ul><p><strong>2. LinkedIn</strong></p><ul><li>Profile should reflect resume.</li><li>Have others endorse you for your skills (both technical and non-technical).</li><li>Be active on groups, share/comment/like tech articles, follow tech companies and leaders.</li></ul><p><em>Make sure to follow companies you are applying for.</em></p><p><strong>3. Projects</strong></p><ul><li>Build at least 3–4. This can be any number really. You could have 2 really <em>good</em> projects that show of your skills, what you don’t want is to have multiple projects poor in quality. The number of projects is up to you.</li><li>If you’re applying for a React role, make sure to have React based projects.</li><li>Push your code to Github as you work on these projects.</li></ul><p><em>You can host the projects for free through Github.</em></p><p><strong>4. Portfolio</strong></p><ul><li>Use a unique domain. It could be your brand, or your name. Mine’s <a href="https://pkayokay.com/">pkayokay.com.</a></li><li>Have your projects on your portfolio to eliminate the barrier of entry. You want to make it easy for the employer to find your projects.</li><li>Be ready to talk about your projects (What did you learn from this project? What was the most difficult part? How did you overcome the challenges that came with this project?)</li></ul><h3><strong>STEP 2</strong></h3><ol><li>Once you have Step 1 done, you’re “ready” to apply. Just do it, be practical.</li><li>Companies usually have a <em>Jobs, or Career </em>section. You can also go to sites like <a href="http://www.glassdoor.com/">Glassdoor</a>, <a href="http://www.indeed.com/">Indeed</a>, <a href="http://www.linkedin.com/">Linkedin</a>, <a href="http://www.ziprecruiter.com/">Ziprecruiter</a>.</li><li>As you apply, make an excel sheet to keep track of job applications (organize as you please). Create the following columns:</li></ol><ul><li>Company name</li><li>Date of Application</li><li>Contact Info</li><li>Follow up: <em>follow up with an email or phone call 2–3 days after applying. Only do this once, don’t be pushy.</em></li><li>Position desired: <em>rate from 1–5 whether this is the role you want, this will help you decide which job to accept if you receive multiple offers.</em></li><li>Chance: <em>mark with low or high. (I will mention this in more detail at the end of the post)</em></li><li>Platform: <em>website/s you applied from.</em></li></ul><p>4.<strong> </strong>Apply on every platform available. If you see a job on LinkedIn and Glassdoor, apply for them on both sites! (this will increase your visibility)</p><p>5. Be honest and sincere</p><ul><li>Do not sound like a machine in your email, be personable.</li><li>A company wants to work with a person who is a good fit. Someone teachable, and easy to get along with (and obviously someone who can do their job).</li></ul><p>6. Network: go to meetups.</p><ul><li>The most valuable thing you’ll get in a meetup is networking with other developers.</li><li>Some of these meet ups will be sponsored by companies/recruiters looking to hire.</li></ul><p>7. Step 1 is the most time consuming, but once you have it done it only takes 15 minutes a day to apply for these roles and follow up. Don’t stop until you receive an offer!</p><h3><strong>Committing to these steps will help you land your first developer job! There’s no harm in trying.</strong></h3><p>If you have any questions about my experience feel free to tweet or DM <a href="http://www.twitter.com/pkayokay">@pkayokay</a></p><p><strong>***Mark a job as high chance if it has…***</strong></p><ul><li>“Junior” in the title.</li><li>General job description.</li><li>Short job description (that lists a small set of skills)</li><li>Years of experience (less than 1–2)</li><li>No listing of degree requirement</li><li>Small company (do some googling to find info about the company)</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=669cef612852" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>