Why I restructured Learn JavaScript

Hey, it’s Zell. Today I want to tell you about an update to Learn JavaScript and a big decision I made.

I made a decision to restructure Learn JavaScript. That means I took whatever I wrote—about 9 chapters (and 60+ lessons)—and rewrote them in a different format.

This was a difficult decision because I wanted to complete and release Learn JavaScript by July 2018. If I did the restructure I won’t be able to complete the course.

Second, I’m afraid I’ll portray the image that I don’t complete projects by the deadlines I set, which in my mind, means people who invested in the preorders don’t get the products in time. I’m afraid that you’ll think badly of me if I do the restructure.

But I still went ahead with it. The question is why.

Traversing the DOM with JavaScript

A good JavaScript developer needs to know how to traverse the DOM—it’s the act of selecting an element from another element.

But why do we need to learn to traverse the DOM? Isn’t document.querySelector enough for most of our needs?

In this article, I’m going to show you why traversing is better that document.querySelector, and how to traverse like a pro. So sit back, relax, and enjoy the article!

How to handle the “bad experience” question

Hey, it’s Zell. Today, we have a question from a student from prefers to remain anonymous. I’m going to call this student May.

Here’s her question:

May freaks out whenever a recruiter asks her to talk about a bad experience in an interview. She had a complicated situation; she didn’t want to blame the company she was at, and she didn’t want to say she lacked experience (and therefore sucked).

She tried to answer the question, didn’t get positive results from her answers, and she’s now considering lying about the bad experience to find a job.

How to build a calculator—part 3

You learned how to build a robust calculator in the previous two lessons. Unfortunately, the code we created together confusing. If you tried to read the code again, you’ll definitely get lost.

That’s why we need to refactor. In this lesson, you’ll learn how to refactor the calculator with some JavaScript best practices.

How to build a calculator—part 2

This is the second part of a three-part lesson about building a calculator. By the end of these three lessons, you should get a calculator that functions exactly like an iPhone calculator (without the +/- and percentage functionalities).

Note: please make sure you finish the first part before starting this article.

You’re going to learn to code for edge cases to make your calculator resilient to weird input patterns in this lesson.

To do so, you have to imagine a troublemaker who tries to break your calculator by hitting keys in the wrong order. Let’s call this troublemaker Tim.

Are you too old to learn to code?

Hey, it’s Zell. Today, we a question from two students, Mark and Todd. They’re in their forties and are getting started in web development, and they are worried that they’re too old. Too old to learn or too old to get a job.

It’s funny I get this question because I felt too old to learn to code when I was 19 years old. It took me six years to before I started to code. When I started, I was 25.

Thinking logically, if I’m too old to learn when I was 19, I should be even more afraid when I was 25. But I wasn’t. I wasn’t afraid because I burned my bridges. I decided I don’t want to work in a bank and decided to learn to design and code. It was a do or die. I couldn’t worry because I had to learn enough to find a job within a year.

How to build a calculator—part 1

This is the start of a three-part lesson about building a calculator. By the end of these three lessons, you should get a calculator that functions exactly like an iPhone calculator (without the +/- and percentage functionalities).

Here’s what you’ll get:

GIF of a calculator you'll build
GIF of a calculator you'll build

Experiment publicly

I’m going to be honest with you. This video is probably going to suck. Why? Because I’m experimenting with something new.

I’m going to tell you what I’m experimenting with, why I’m experimenting and why you should conduct your own public experiment.

Case study—a project from hell

Project T is a project that I don’t want to remember. It was a big project for a big company—a project that I thought I would be proud to include in my portfolio; and boy, I was wrong.

Project T was bad. It lasted nine months when it was supposed to last three months. At the end, I gave a huge discount to the agency because they lost money on the project; as a result, I lost big time too.

Of the original team—a project manager, a visual designer, a UX designer and a frontend developer (me), I was the only member that survived the project till the end. Largely because of two reasons:

  1. I was stupid and naive
  2. My sense of responsibility didn’t allow me to abandon the project halfway.

By the end of the 9-month long project, I was burned out, and I quit freelancing for a year.

Hold on while i sign you up…

Woohoo! You’re in!
Now, hold on while I redirect you.