Common Code Errors

Share This Post

Anytime you are coding, errors are going to occur. As you gain experience, you will get better at either not making errors, or recognizing errors and why they occur. Let’s take a look at some common errors to understand them and why they occur.

Reference Error

This error occurs when a reference is made to a variable that does not exist. Imagine we have a variable…

let animalName = ‘Bongo’;

If we log the variable to the console, it will print out “Bongo”…

console.log( animalName );

Side note: the console is a tool within modern browsers that you will use often in your JavaScript programming. To access the console, hit F12, or go through your browser menu to the developer tools. You will see that console is one of the tabs. The console object has methods that we can use in programming. One of them is log(). The log() method allows the information within the parentheses to display in the console area.

Imagine we made an error and misspelled the variable…

console.log( animalNme );

This would result in a reference error. The console would report ReferenceError: animalNme is not defined. It is also helpful that the console shows the line number where the error occurs.

This error would also occur if we do not create our variables.

If we log the variable to the console without first creating it…

console.log( animalName );

The console would report ReferenceError: animalName is not defined.

Another reference error is when we create the variable, but do not initialize it with a value…

let animalName;

If we log the variable to the console, it will print out undefined…

console.log( animalName );

It is a recommended practice to initialize your variables upon creation. If you do need to set a variable to an empty value, it is a recommended practice to set it to null.

Happy Coding!

Clay Hess

More To Explore


Demystifying Scrum User Stories Confirmation: Ensuring Quality and Collaboration

One of the key elements of Scrum is the use of user stories to define the requirements of a system or feature from the perspective of the end user. As teams work through the product backlog, it becomes crucial to confirm the user stories to ensure they meet the desired criteria and are ready for development. In this blog post, we’ll explore the concept of Scrum user stories confirmation and its significance in delivering high-quality products.


The Power of Conversations in Scrum User Stories

At the heart of Scrum lies the concept of user stories, which serve as a means of capturing requirements from the perspective of end-users. However, the true power of user stories lies not just in their written form but also in the conversations that take place around them. In this blog post, we will explore the significance of conversations in Scrum user stories and how they contribute to the success of Agile projects.

Do You Want To Boost Your Business?

drop us a line and keep in touch

Scroll to Top

Need help?

Let's have a chat...


Jump Back In!

Here at Webolution Designs, we love to learn. This includes sharing things we have learned with you. 


Begin Your Learning Journey Today!

Come back inside to continue your learning journey.