Developers: Learn How to Use Conditions
As a developer or software engineer, writing code that can handle different situations is crucial. This is where conditions come in. Conditions allow you to execute different blocks of code based on certain criteria being met. In this article, we’ll take a look at how to use conditions in your code, specifically focusing on JavaScript.
What are Conditions?
Conditions are statements that can be used to control the flow of a program. They allow you to specify different actions to be taken based on whether a certain condition is true or false. In JavaScript, conditions are typically written using if, else if, and else statements.
Using Conditions in JavaScript
Let’s take a look at a simple example of using conditions in JavaScript. Suppose we want to write a function that checks whether a given number is even or odd. We can achieve this using an if…else statement:
function checkEvenOrOdd(num) {
if (num % 2 === 0) {
console.log(num + ' is even');
} else {
console.log(num + ' is odd');
}
}
In this example, we’re using the % operator to check if the number is divisible by 2 (i.e., if it’s even). If the condition is true, we log that the number is even; otherwise, we log that it’s odd.
Advanced Conditions
In addition to simple if…else statements, JavaScript also supports more complex conditions using else if and switch statements. These can be useful when you need to handle multiple cases. Additionally, you can use logical operators such as && (and), || (or), and ! (not) to create more sophisticated conditions.
Conclusion
Conditions are a fundamental concept in programming and are essential for writing robust and flexible code. As a developer or software engineer, mastering the use of conditions will enable you to create more dynamic and responsive applications. Take the time to practice using conditions in your code and explore the various ways they can be applied. With a solid understanding of conditions, you’ll be well-equipped to tackle a wide range of programming challenges.
Some people really make it 3 or 4 nested conditions while what could be done in 1 or 2.
what if you integrated both if into one if statement ??
like
if (!post && post.authorId !== userId) {
throw new Error(" Post doesn't exist or your're not the ownwer of this post.")
}
this was it's becoming more shorter, what do you think man?? I don't know I'm still learning, just asking you.
This concept is a great one to implement in functions to improve readability ! To add a bit to the discussion, in the video you state it's called "nexted conditions", little type, it's "nested conditions". The paradigme used to improve readability is called inversion. anyone who wants to learn more about this can search about "never nesters", which is what developpers who absolutely hate nesting conditions call themselves. On my own work, sometime I struggle to use that because I don't really know how to define what should be a condition and what shouldn't, usually in the main codebase I work with, post handling is done in the controller, and that will always nest everything inside a condition to check if the post exists. I don't really know what implementation I could do to prevent that yet.. Great concept !
Plus de ça