If ‘IFs’ and Buts Were Candy…

Share This Post

We can program in such a way as to have our code make decisions for the end user. This logic can make for a better user experience and more intuitive program. One of the basic building blocks is an IF statement.

An IF statement decides whether something is true or false (boolean). Based upon the answer, appropriate code is run. Here is the basic syntax…

[code lang=”js”]
if(something is true){
// Then do something
}
[/code]

That’s it. That is all there is to it. The key is to remember that IF statements always test boolean…true/false…yes/no. Here is another example…

[code lang=”js”]
if(10 === 10{
alert(‘The tens are equal’);
}
[/code]

The aforementioned code would alert the end user that the tens were equal because it is true that 10 is equal to 10.

So that is one done with hard-coded values, but, typically, we use variables within our IF statements. Here is an example…

[code lang=”js”]
// Create variables to hold data
var firstNum = 10;
var secondNum = 10;
// Compare the two variables
if(firstNum === secondNum){
alert(‘The variables are equal’);
}
[/code]

So, as you can see, we can compare two variables to test whether the comparison is true or false. Over the next several posts, I will add more nuances to the IF statements. Before long, you will see how useful they can be.

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.