News for hackers. Stuff that matters.

A comment on Most common mistakes during interviews. Parent comment

Re:Most common mistakes during interviews by alpha_squared on Sunday August 30, 2020 @02:03PM (#24324604)
> Sometimes it's not 100% clear if you're just coming in that a function returns a boolean

I'd argue the function isn't named appropriately, then.

> Sometimes you just want to remind yourself and it sneaks past a code review

Remind yourself what, exactly?

> dozen plus languages, and some just handle truthiness differently and it's easier to just make sure (looking at you, Javascript)

I'd argue that it's on the developer to know and work with the language's semantics (and I say this as someone who's not a fan of JS). Trying to write code that is nearly language agnostic in semantics will leave out a whole lot of language-specific value.

[ Parent | on HN ]
Re:Most common mistakes during interviews by RandoHolmes on Sunday August 30, 2020 @02:16PM (#24324712)
> I'd argue the function isn't named appropriately, then.

Maybe yes, maybe no. The point is that adding "== true" makes it more clear and should therefore be done.

[ Parent | on HN ]
Re:Most common mistakes during interviews by coin on Sunday August 30, 2020 @03:25PM (#24325214)
For strongly type languages (like Java), how can ==true make it more clear?
[ Parent | on HN ]