jonhess

Yeah, redundancy and efficiency are opposites. As engineers, we always chase efficiency, but resilience and redundancy are related.

which also explains why ternary logic puzzles are so elegant.

Could you elaborate on that?

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.

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]

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.