What ‘Defines’ You?

Share This Post

In our continuing Data Type saga, I want to turn our attention to some specialized data types.

  • Undefined
  • Null

These are used in specific circumstances and do not mean the same thing. These are what I would call ‘quasi-data types’. What I mean by that is that you typically do not set out to create a variable as undefined or null (sometimes). But knowing these and how they typically work and can be utilized in our programming can be helpful.


A variable is undefined when it has not been assigned any data. Typically, you do not want to have variables that are undefined, but is happens sometimes. When it does occur, it usually means your code is broken. Here is an example…

[code lang=”js”]
var myVariable;

In the code above, I create a variable (myVariable), but I do not instantiate it. It is created, but nothing is in it, therefore, it is undefined. So the document write statement would fail. To avoid this, you typically assign a value out of the gate. This would avoid the undefined error and allow you to test that variable. For example, if I set the value of myVariable to zero (0), then I could test if it is zero. If it is, then I know it has not been set yet.

[code lang=”js”]
var myVariable = 0;
if(myVariable == 0) {
// Do something;


Nulls, which some have equated with undefineds, are not undefined. Nulls are objects and undefineds are not. The reason some have equated null with undefined is because if you test undefined == null, this returns true. The problem with this is ‘==’ performs type coercion. Proper equality testing would utilize ‘===’, which does not perform the type coercion.

We can test for nulls as follows…

[code lang=”js”]
var myVariable = null;
if (myVariable === null) {
// Do something

So we can check if a variable has been defined or not and we can even test whether a variable is null or not. Then, our code can make decisions based upon the results.

Happy Coding!

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.