JavaScript
Of JavaScript's many confusing aspects, the keyword this can be one of the most complicated -- Here's a joke about the troublesome keyword: Sometimes when I'm writing Javascript I want to throw up my hands and say "this is bullshit!" but I can never remember what "this" refers to — Ben
General
Nothing is more discouraging than having spent months of effort learning JavaScript, reading dozens of articles and books, grinding through countless lessons and tutorials, only to have no idea how to do any of it by yourself. It turns out that those courses you took didn't completely prepare you to
JavaScript
Learning JavaScript, there's a question that burns in everyone's mind: "When will I be done? When will I finally be an expert?" - You've fought hard, toiled for months, and you have a good grasp of the basics, but how long until you finish? After all this effort, you still
JavaScript
When you see someone on Udemy promising to take you from JavaScript Zero to JavaScript Hero in only 2 weeks, it's easy to be skeptical. What about courses like FreeCodeCamp? Can you actually become a developer solely by doing an online course? The answer is... kind of. To be a
It's happened to all of us. After much toil, we've finally finished a website - no, a work of art. Everything runs perfectly - animations are smooth, the layout is robust, and everything looks polished, perfect... but then you open it in Edge. Your stomach drops - It looks awful.
JavaScript
If you're a newbie when it comes to web development and security, it can be difficult to imagine exactly how a website gets hacked. When we create a website, it only runs the code we write - so how can someone use it to run code on someone else's machine?
If you try to learn React, Vue, or Angular as a beginner, the first piece of advice you get is to go learn JavaScript - anyone without some JavaScript experience is going to struggle with the added learning curve presented by a framework. What isn't discussed is how much JavaScript
Have you ever added a button to a page with JavaScript expecting it to function fully, but when you clicked it nothing happened? You've double checked your code - you're creating the event listeners, the selectors are correct, but it's still not working! Chances are, if you've hit this situation,
Closures, as well as being a favourite interview question, are one of the more confusing parts of JavaScript. Despite the wealth of articles offering explanations of closures, there are dozens of threads on reddit and other forums asking for more help with closures. It's not hard to see why, since
I'm not going to lie - I used to struggle writing comments. I have wasted hours writing comments that aren't helpful to anyone, while leaving out comments that have cost me hours of debugging time. As we learn to code, we get taught to write comments early. In FreeCodeCamp's curriculum,
Here's the question: What's the difference between these two methods of creating a function? function a() { //This is known as a function declaration console.log("Hello"); } var b = function() { //This is known as a function expression console.log("World"); } Both of these methods do almost the same thing, however there
Let's be honest. We all write bad code. Sometimes, we write absolutely shocking code. In the programming community, we have an obsession with "good" code – and it's not difficult to see why. Good code is objectively better than bad code. It's faster, cleaner, more maintainable – Why would you settle for
Basics
UPDATE: There is now an aspect-ratio CSS property which can be used to set the ratio between width and height. The best way to make a square is now aspect-ratio: 1 / 1 If you remember the days of floats and table layouts, display: flex is absolutely magical... until you want
When you start working in Javascript and building apps and webpages, you get used to running code based on inputs - someone pressed a button, and then your code gets to run. This is fine for most webpages, but what if you want to to make changes on the page
When we learn to write code, we spend a lot of our time doing exactly that - writing code. As we transition into careers and larger projects however, we find out that we actually spend most of our time reading code - and we quickly learn that developers can't write
Let's face it, writing unit tests is hard. Many new coders take a long time to get into unit testing. They're scary, a lot of effort, and it's difficult to understand how they work. When we do eek out a few unit tests, they don't seem to be proving anything.
Carl Anderson