How I Learned To Code In 6 Months & Got a Job Offer (self-taught)
Tags: job, frontend, learning, beginners
Published: 2023-07-24 05:41:26

<p data-pm-slice="1 1 []">I quit my job in April 2021, self-taught programming/web development &amp; landed a <strong>Remote Full Stack job</strong> in November 2021 (based in Vancouver, Canada), all without spending a dime. Figured someone might find a factual time history of my experience useful -_- Net amount of LeetCode time was 0 hours.</p>
<img src="https://miro.medium.com/v2/resize:fit:700/1*eA39Oxpm1IQKFgK0VIRfKw.png" alt="" align="left" />

My Acceptance Email
<h1><strong>Table of Contents</strong></h1>
<em>- Learning Progression / Tech Timeline / Resources</em>

- <em>Greatest Challenges &amp; How I Overcame Them</em>

- <em>Major Takeaways / Key Learnings (If I were to start over)</em>
<h1><strong>Disclaimer</strong></h1>
The timeline is an un-opinionated, fact-for-fact rundown of my experience; the remainder is obviously just my opinion based on my experiences.
<h1><strong>Learning Progression / Tech Timeline / Resources</strong></h1>
For this section, i’ll walk through my experience and summarize each step, and add my personal timeline for that learning progression. I had no prior programming experience, so we’re starting fresh.

<strong>To begin</strong>, I had a conversation with three of my friends who were Software Engineers, asking for any resources they had to learn programming. One friend recommended I learn <strong>JavaScript</strong> from <a href="http://FreeCodeCamp.org" target="_blank" rel="noopener noreferrer nofollow">FreeCodeCamp.org</a>, completing their <strong>JavaScript Algorithms and Data Structures</strong> course.
<ol>
 	<li><em>Learn JavaScript — FreeCodeCamp’s JavaScript Algorithms and Data Structures course (2–4 weeks, 3–4 hours per day).</em></li>
</ol>
This course was highly interactive, and I stepped through the learning hurdles in JavaScript really smoothly. They provide an excellent topic description and then give you a challenge to complete each concept inside of their own Integrated Development Environment (IDE).

The challenges were all at an appropriate difficulty level, and if I could not solve a challenge, their answers were very explicit and easy to understand. This certificate says it takes 300 hours, but I found this to be a fairly conservative estimate.

<strong>Step 2</strong>, was to complete their <strong>Responsive Web Design</strong> certificate. At this point, I had come to note that HTML CSS &amp; JavaScript was the essential trio to get liftoff, so this HTML &amp; CSS certificate was the natural progression.

2) <em>Learn HTML &amp; CSS — FreeCodeCamp’s Responsive Web Design Certificate (2–4 weeks, 3–4 hours daily).</em>

<strong>Step 3</strong>; Upon completing the Responsive Web Design certificate, I started applying for jobs; not sure where that audacity came from, but I quickly learned that this level of accreditation was insufficient. Every job posting wanted me to link my portfolio website, which I didn’t have, and honestly, I still didn’t know how to develop or deploy a website at this point (I had just been using FreeCodeCamp’s IDE).

So I completed <a class="af oy" href="https://www.youtube.com/watch?v=_xkSvufmjEs" target="_blank" rel="noopener noreferrer nofollow">Kevin Powell’s Web Portfolio YouTube</a> tutorial (2hrs). I also downloaded Visual Studio to code it. This tutorial finished off with purchasing a domain and hosting the project, so it was live; a great experience.

3) <em>Finishing this portfolio project; launching my first HTML &amp; CSS static website (10–15hrs).</em>

And now, I had a portfolio, but I had no projects inside said portfolio, so this nicely introduces step 4.

<strong>Step 4</strong>; For step 4, I looked at job postings for the jobs I wanted to see what skills I didn’t have. This information would guide the direction of my projects, which is critical because they are the only real credibility you have to your name. Nearly every posting requested React, so I learned React Native from <a class="af oy" href="https://www.youtube.com/watch?v=qSRrxpdMpVc&amp;t=10372s" target="_blank" rel="noopener noreferrer nofollow">Academinds React-Native YouTube</a> tutorial (5hrs).

4.1) <em>Finish Academind’s React-Native Youtube tutorial (20hrs).</em>

Following this tutorial, I had all the essential skills to develop my own basic CRUD mobile app; a Todo app. I stylized it myself, so it looked atrocious, but I ultimately deployed it to the app store and added it to my portfolio.

4.2) <em>Code my React-Native app with basic CRUD functionality [read/write to device localstorage] | (1–2 weeks).</em>

<strong>Step 5</strong>; Waste a whole lot of time on random little youtube tutorials that I didn’t understand [t<em>his step is not mandatory to follow but I was directionless] (1 month)</em>.

<strong>Step 6</strong>; After a period of aimless meandering, I finally found some direction and inspiration for my second project. I would occasionally put out job applications, get no response, so I knew I needed something more.

I settled on building an E-commerce store with <strong>Stripe &amp; React</strong>, following another youtube tutorial at approximately 5hrs in length (can’t find the link for my life:’[). After completing the tutorial, I rebranded the site, added my products, and made zero sales; nice. Still, another project to the portfolio, all hosted live and everything.

6) <em>Code a functional E-commerce store in React + Stripe + Commerce.js (1–2 weeks)</em>.

<strong>Step 7</strong>; Still no job response — lame. Time to start diversifying my applications away from Frontend alone, branching outwards to include Backend and Full Stack. This was achieved by learning Node.js + Express.js + MongoDB. This took me a while, and in retrospect, I would break down this step into two parts if I did it again. Part 1 would be learning a bit about networking and HTTP requests etc, and then part 2 would be learning Node.js + Express.js and running a server.

7) <em>Learn a bit about Node.js, Express.js &amp; servers (1- weeks).</em>

Nothing came out of this stage, except I had a bunch of random GitHub repos that didn’t do me much good.

<strong>Step 8</strong>; Step 8 was my first <strong>Full Stack</strong> project and also my lucky number 3 project. This one took me ages, and it used React + Firebase Auth + Firestore DB tech stack. Deployed on Netlify.

Firebase is a Paas service which basically means that handles all the backend stuff for you and makes it super easy for you to develop full-stack applications without the hassle of deploying a Node.js + MongoDB backend with JWT auth and then having everyone hack it to pieces as soon as it’s live.

It was super convenient, and I found it a great compromise for getting a handle on Full Stack Development.

8) <em>First Full Stack CRUD project with React + Firebase [auth + db] (1 month).</em>

To get started on Full Stack development with Firebase, I watched a tutorial demonstrating how to implement Firebase Auth in a React project and covered protected routes.

From there, it was super easy to bring in the Firestore database just by reading their documentation and having all the CRUD functionality hidden behind an authentication wall, where each CRUD function was associated with a user ID that is created when you use Firebase Auth.

<strong>Step 9</strong>; Applying for 3–4 jobs per day. I had three projects, and I felt I had a good array of technology demonstrated across the projects in my portfolio.

Adding some Full Stack/DB+Auth stuff helped boost my response numbers. I also learned Python because every job seemed to be looking for it.

This took me half of a 5hr Data Science YouTube tutorial. Super easy to translate from JavaScript to Python, in my experience.

9) <em>Apply for jobs (1–2months) + learn Python (3–5hrs).</em>

<strong>Total experience around 6 months, averaging 4–5hrs per day, 5–6 days per week.</strong>
<h1><strong>Greatest Challenges &amp; How I Overcame Them</strong></h1>
The two challenges I found that were a real pain were: <em>Imposter Syndrome</em> and <em>Tutorial Hell.</em>

<strong>Imposter Syndrome</strong> was a real pain because I had no support or network for reassurance. And every job I applied for had around 200 applicants; what a pain, really demotivating and demoralizing.

For me, the solution was to realize two key things. The first was that it’s not really a continuous spectrum of developers. It’s a pragmatic world, and we’re not all ranked; more analogous to a discrete system of <strong><em>Can code a Full Stack app</em></strong> and <strong><em>Can’t code a Full Stack app</em></strong>*.* You can or can’t; it doesn’t matter if people are way better than you as long as you can both code a Full Stack app.

The second thing to realize was that I needed to shift my focus; less on how good people were at developing and more on how good I was as a learner. People can be better developers than me, but what matters more for junior SWE roles is that you’re a good learner.

You know how to research, you can give it a shot, and you are receptive to feedback. Helped me not care about how good everyone else was with their snarky SWE qualifications.

<strong>Tutorial Hell</strong> was also a mofo, but the solution is actually chill. I found that I just had to start off making super minor changes to the tutorials I followed.

Starts off just being a font size, text color, or background picture, and then it just snowballs out of control until you have a new application. Adapting some of the logic stuff is good too, you really understand how it all works, which means it’s way easier to reproduce.
<h1><strong>Major Takeaways / Key Learnings (If I were to start over)</strong></h1>
<strong>Fastest Way to Learn Coding (in my experience)</strong>

This tip is outside of learning basic HTML CSS &amp; JavaScript and is more about general programming thereafter — the fastest way to learn HTML CSS &amp; JavaScript is FreeCodeCamp. For everything else, the system I use is as follows:
<ol>
 	<li>Find a good tutorial or article that describes a new concept.</li>
 	<li>Code out said tutorial for myself.</li>
 	<li><em>Critical</em> Leave loads of comments with explanations on functionalities all throughout my code (guarantees you understand everything and further solidifies memories).</li>
 	<li>Save code to GitHub.</li>
 	<li>Adapt the project; keep the same code skeleton, but repurpose the project into my project (this might be a new color scheme, layout, or functionality). An example would be to follow a tutorial for a CRUD app with Auth + DB. I would keep Auth + DB system, rework the layout and app function and update the CRUD system accordingly.</li>
 	<li>Save new projects to GitHub.</li>
 	<li>Whenever I start a new project that I know will use a similar infrastructure, first 2–3 projects like I’ll revisit the GitHub repo with all the amazing comments I left myself. After that, I can generally remember if it’s something I do often (which is convenient as I naturally end up remembering only the relevant stuff).</li>
</ol>
<strong>Resume</strong>

<a href="https://www.reddit.com/r/jobs/comments/7y8k6p/im_an_exrecruiter_for_some_of_the_top_companies/" target="_blank" rel="noopener noreferrer nofollow">https://www.reddit.com/r/jobs/comments/7y8k6p/im_an_exrecruiter_for_some_of_the_top_companies/</a>

<strong>Cover Letter</strong>

<a href="https://www.reddit.com/r/jobs/comments/37rgr1/heres_the_best_cover_letter_ive_ever_seen/" target="_blank" rel="noopener noreferrer nofollow">https://www.reddit.com/r/jobs/comments/37rgr1/heres_the_best_cover_letter_ive_ever_seen/</a>

<strong>GitHub</strong>

Best to get one <em>ASAP.</em> Employers and hiring people apparently go mental over the activity log. The sooner you can start committing code to your GitHub and getting your activity up, the better cause it is the #1 way to show the duration and intensity of your experience. You get one 3 months late, and you miss out on bragging about 3 months of dev time. I’d recommend committing a minimum of 1 thing per day, so the whole thing is green patches (even if it’s just adding a meaningless comment to a repo and pushing that commit).

<strong>Applying for Jobs/Networking</strong>

Basically just need a simple &amp; clean portfolio with some contact details, about you section, and 3 projects.

Each project should have a link to the live page and the GitHub repo. GitHub repos should be tidy; ideally, each project would have a nice <a href="http://Readme.md" target="_blank" rel="noopener noreferrer nofollow">Readme.md</a> file that details the project. The 3 projects should be pinned to the top of your GitHub.

Your LinkedIn page should also be clean but doesn’t need OTT. Just shows your previous experience and how it relates to the job you want (generally, most roles demonstrate problem-solving, communication, and leadership).

<em>Critical</em> For each job you put out, find someone senior in that company's tech department or the hiring manager/person themselves. Connect with them on LinkedIn and append the following note:

<em>Hi [name],</em>
<em>I hope this message finds you well.</em>
<em>I just noticed your job posting for a [insert_job_posting_title] and as a seasoned [insert_your_relevant_role_experience], I feel I would be a great fit for the role.</em>
<em>I’d love to connect and chat about the opportunity.</em>
<em>Cheers, [your_name]</em>

Literally gets you free interviews (it also got me an earlier offer — I didn’t go forwards with it).

<strong>Communication/Soft Skills</strong>

This ultimately landed me my job. I was initially rejected cause the role was full (I applied late), and a week later, the hiring dude came back to me and said he liked my communication skills and said they wanted to make something work.

What good communication meant for me was, for every meeting, send a follow-up email saying ‘Thanks for your time’, ‘Very grateful for the opportunity to meet you and your team, and hear about what you’re doing’, ‘Take care’; all these kind of things.

Even when I was rejected, I followed up by saying, ‘Thanks a lot, I learned heaps and am very appreciative for the experience and your time’ or something along those lines. I actually think it was my response to rejection that was the key one, but just generally, if you can demonstrate gratitude and the desire to learn and improve, you’ll be right.

Thanks for reading. If you find this post exciting, find more exciting posts on <a class="attrlink" href="http://blog.learnhub.africa/" target="_blank" rel="noopener noreferrer nofollow">Learnhub Blog</a>; we write everything tech from <a class="attrlink" href="https://blog.learnhub.africa/category/cloud-computing/" target="_blank" rel="noopener noreferrer nofollow">Cloud computing</a> to <a class="attrlink" href="https://blog.learnhub.africa/category/frontend/" target="_blank" rel="noopener noreferrer nofollow">Frontend Dev</a>, <a class="attrlink" href="https://blog.learnhub.africa/category/security/" target="_blank" rel="noopener noreferrer nofollow">Cybersecurity</a>, <a class="attrlink" href="https://blog.learnhub.africa/category/data-science/" target="_blank" rel="noopener noreferrer nofollow">AI</a>, and <a class="attrlink" href="https://blog.learnhub.africa/category/blockchain/" target="_blank" rel="noopener noreferrer nofollow">Blockchain</a>.

This article was written by<a href="https://medium.com/@_Smoljames"> James McArthur</a>