> which also explains why ternary logic puzzles are so elegant.

Could you elaborate on that?

There’s an island of 100 people who are incapable of communicating with each other, besides what they can see with their own eyes. No one can see their own eye color. Everyone knows that there are only blue or brown eyes. One day a fairy appears before the islanders and says that at noon each day, islanders will be given a chance to leave if they know their own eye color. The fairy concludes the rules at 11am and also adds that at least one islander has brown eyes. That is Day 1.

On what day, in the longest case scenario, have all the islanders left? You can assume they are perfectly logical, and no guessing is allowed obviously.

There are also no tricks like mirrors or water or anything like that. It’s a logic puzzle not a lateral thinking one.

The solution demonstrates ternary logic.

This initially bothered me too.

The macOS equivalents are command+left-arrow and command+right-arrow. I find them even easier to invoke than home/end.

That’s what I like about this game too. It quickly turns into a concurrency / lock contention optimization problem if you build a very connected network.

Command-e, put the selected text on the find clipboard.

Then command-e, command-g (find next) will search for the selected text without sacrificing the copy/paste clipboard.

Also, the find clipboard is shared between apps, so you can command-e in Safari, then command-g in Xcode.

Get Alfred. Clipboard history will change your life.

I've been using Copy'em Paste but Alfred looks like a beast.

It is a beast. If you are a dev you can extend it with scripts.

And eject a disk from the desktop.

Note, cmd+e seems to be a safari thing; no such luck in chrome. I just cmd+f again.

> cmd+e seems to be a safari thing

Works fine on Firefox. I'd say breaking it is a Chrome thing.

Actually, doesn't work for me in Firefox (68.0.1)

In chrome, cmd+e updates the search text, cmd+g starts the search and iterates through results, shift+cmd+g goes backward through the results

The lookup happens on each invocation. It’s alway indirect, and the implementation of a method can be changed at runtime. Method calls aren’t optimized to be direct invocations.

If you're writing a desktop app, you may need to debug frameworks and libraries you don't have the source for. If you author a framework or library, you may need to debug a client application you don't have source for. In both cases, you'll likely need to debug assembly code.

I've seen set top boxes that offer three answers to yes/no questions.

"Switching the channel will switch to live mode and lose your rewind buffer. Do you want to switch to channels?"

[YES] [NO] [Cancel]

I've had to implement an industry-standard medical protocol which had 6 values for "sex".

The more the merrier!

State of California used to allow 5 in healthcare reporting: male, female, indeterminate, unknown, and other.

The first two are largely self-explanatory, self-identification issues largely not considered. "Indeterminate" means that evidence is present but it's not possible to distinguish. "Unknown" means evidence isn't present (and hence it's not possible to make a determination. Example: unidentified human remains found and either grossly mutilated or partial to the point of not being able to determine sex. "Other" means that evidence is present, and it's possible to make a determination, but it doesn't fit any of the previous categories.

There are diminishing returns to going deeper and deeper. But there's a big return for the first level.

I think it's useful to have a basic understanding of assembly so that you can debug better, or understand why some behaviors are undefined. I think that only takes a basic understanding of assembly though.

If you want to be an expert at assembly, you probably want to go deeper, but most people don't have that goal.