News for hackers. Stuff that matters.

A comment on Most common mistakes during interviews. Parent comment

Re:Most common mistakes during interviews by RandoHolmes on Sunday August 30, 2020 @02:19PM (#24324732)
> do this sometimes if it makes the code clearer.

As do I, the above poster is just super judgemental and probably not a lot of fun to work with.

An observation I've had over the years is that often times developers will come to conclusions that they ought not to. The idea that typing out "== false" indicates you don't understand bools is a non-sequitur.

[ Parent | on HN ]
Re:Most common mistakes during interviews by xorcist on Monday August 31, 2020 @03:41PM (#24335202)
When could an extra "== true" or "== false" possibly make anything clearer?

  if not (x > 5)
looks normal,

  if (x > 5) == false { .. ]
is just confusing.

Why would it matter if a function returned a boolean? It's either compared for truthiness, or the comparison for truthiness or compared for truthiness, even in the most dynamic languages.

[ Parent | on HN ]