puzzlers

In Java, the puzzlers are worth collecting precisely because you think of it as a simple language.

Let's use an exemple from Java Puzzlers (Joshua Bloch and Neal Gafter): char x = 'X'; int i = 0; System.out.print(true?

The Car Talk puzzlers are straight forward and should be taken at face value.

Was the interview about stuff they need to get done, or doofy puzzlers?

I myself have been subjected to brain teasers and puzzlers in technical interviews well within this 10 year window.

I'd appreciate it, if someone can share a few more links with similar puzzlers on the web.

My experience with puzzlers is that average people like to feel superior for knowing the answers to a puzzle that someone else doesn't know.

I miss the old times when these puzzlers were asked during interviews.

Happy to test and spread it around to other puzzlers I know.

There are plenty of good puzzlers out there that I've enjoyed.

And those puzzlers were themselves introduced by the authors with the proviso that Java has remarkably few quirks for something so very large, and that this is/was tremendous progress.

There are some confusing parts of the manual that get posted around on the Internet as puzzlers, like integer promotion rules, undefined behavior, sequence points, etc.

That road leads to "how many golfballs in a minibus" type of puzzlers and we already have data now that shows that those things don't work.

I wholeheartedly disagree with this statement: > People like to pose puzzlers to “see how people think” but that’s nonsense in the case of puzzler questions.

Sometimes folks call these "puzzlers" but I think they're unfairly lumped in with true "puzzlers" - crap like "why is a manhole round" where there's a right answer that depends on either experience or some specific insight.

If you look at Kotlin, it's basically advertised as resolving around half of the famous Java Puzzlers.

You haven't seen a book called C Puzzlers.