A brief intro 🔗When we think about technical writing such as documenting code, or writing articles, we can see some very obvious benefits, like: The code is easier to understand to others but also to you. You help others to learn. It can improve your CV. And you could even commercially profit from it. And yes, I knew this stuff before I started. However, some time ago I decided that I was going to write articles specially about JavaScript, a language I like, so like 8 weeks ago I started writing articles in the DEV Community and I did it without knowing all the benefits I would get from it.

In the previous part of this series I talked about how you can shorten your conditionals with truthy and falsy values. So if you haven’t read that one I would recommend that you do cause this is a continuation, Link here! In the past article I mentioned about string interpolation and how does the ternary operator becomes handy in these cases, however I knew that there was a lot more to say about it.

In the previous part of this series I talked about how you can shorten your conditionals with truthy and falsy values. So if you haven’t read that one I would recommend that you do cause this is a continuation, Link here! Probably in some occasion you have seen pieces of JS code from other programmers and suddenly you saw something like a question mark (?) and then a colon (:) and maybe you didn’t knew what was going on there, I remember this happened to me and I felt a little confused, but after I learned this I realized how handy and useful it is in so many situations.

In the previous part of this series I talked about how you can shorten your conditionals with truthy and falsy values. So if you haven’t read that one I would recommend that you do cause this is a continuation, Link here! Probably you have realized of how hard and confusing can it be to read a long conditional… Let me give you a few examples of that and later in the post I’ll give you better solutions to them: