Has anyone asked you whether you are a real developer?
Has anyone ever told you in your face that you’re not a real developer?
The important part is not what they think. It’s what you think.
I’m a weirdo. I’m always working (either coding or teaching you how to code). I code on during work, at night, and even on weekends. I can’t seem to separate myself from work.
Recently, I learned to relax. I discovered that one of my favorite activities is to watch movies. I only watch some of them though. For example, I chase after every movie in the Marvel universe (for Avengers), but I don’t watch anything related to Star Wars.
But why? Are Marvel movies better made than Star Wars? Do they contain more compelling stories? Do they have better actions and effects?
I wanted to know why I watched some movies and not others, so I dug into my own psychology (like I said, I’m a weirdo; forgive me for doing weird things). I found a surprising reason. I can even use this reason to explain how I learned to code 😂.
A student asked why I switched over from Sublime Text to Visual Studio Code, and he’s wondering whether he should switch too.
Here’s a quick answer to that question.
I had an exciting experience three weeks ago—I gave my first Chinese talk at the 4th CSS Conference in China, in Xiamen, on March 31st.
I learned a lot from this experience—both about myself and about the chinese development scene—and I want share my learnings with you.
Let me begin by introducing the organizer duo.
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.
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!
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.
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.
Today, I want to share a disturbing truth about finding a job. This may just change the way you think about how you find a job, especially if you are starting out.
You ready? Here it goes.
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.