There's one key qualifier in this sentence: I know. One's skill set matters, I guess...
The post talks about how to avoid ifs ;)
In unit tests, assertions inside if-clauses risk being silently skipped. We discuss some tips and best practices to avoid situations where assertions live in if-clauses.

Generally, it is inadvisable to directly expect in if-clauses. Here are some tips to avoid these situations.
Using a third-party library when it's applicable definitely works. Much of this post is for those who can't add a heavy dependency :)
Type guards rely on the programmer to be correctly defined and are error-prone. We introduce the type extractor💡, which may be a safer alternative in many scenarios.

A trick that I'd like sharing :)
Oops, seems like already dead :\
I would just use the part that I consider good.