Inequality for all!

Share This Post

In my last post, I talked about comparisons using equality. Today, I want to talk about inequality. There might be situations where you want to check to make sure two items are NOT equal to each other. So how would we do that? We would use the not equal operator (!=). The exclamation point is known commonly as the not operator. There are various situations to use the exclamation point. Here is an example of not equal…

[code lang=”js”]
// Not equal example
var yourNum = 5;
var myNum = 3;
if(yourNum != myNum){
// Do something as a result of not being equal
}
[/code]

The aforementioned condition statement would return true because the variables yourNum (5) is not equal to myNum (3).

In my previous post, I also spoke of absolute comparisons….meaning comparing values and type with the triple equals signs (===). We can do the same thing with not equals by adding an equals sing…!==. So using this (!==) is asking if it is absolutely not equal. First lets look at an example that uses a single equal sing…

[code lang=”js”]
// Not equal example just comparing values
var firstNum = 5;
var secondNum = "5";
if(firstNum != secondNum){
// Do something
}
[/code]

In the above code, the ‘do something’ section within the curly braces would not run because the condition statement would return false. This is because the value of firstNum (5) is equal to the value of secondNum (“5″). Now let’s add an equal sign…

[code lang=”js”]
// Not equal example just comparing values
var firstNum = 5;
var secondNum = "5";
if(firstNum !== secondNum){
// Do something
}
[/code]

This code would return true because firstNum is not absolutely equal to secondNum. They are equal in value (5 == 5), but not in type (integer != string).

Rule of thumb…use absolutes as often as possible…so add the extra equal sign.

Happy Coding!

Clay Hess

More To Explore

Code

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.

Code

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
small_c_popup.png

Need help?

Let's have a chat...


Login

Jump Back In!

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

Register

Begin Your Learning Journey Today!

Come back inside to continue your learning journey.