Zen master says: the real issue resolution is within yourself.

That documentation sounds like marriage.

“allegedly written”

human tools

What a mad man, using quotation marks in memes!

Cabin in the Woods!

Control is surprisingly fun. Got it on GoG.

Specifically for the rate limit issue, a lot of nix’s derivations are hosted on GitHub and now and then the rate limit problem comes up when I rebuilds a dev environment.

Nixos.org is kind enough to host gigabytes of cache, but to get a ~40MiB tarball, we need to beg at the door of M$. Path dependency is really a trap.

J Moore, the Moore in the wildly used Boyer-Moore string search algorithm, has a first name of a single letter, J. It’s not an abbreviation.

Haha, but it’s really a pack of tools, more like a toolbox.

In recent git versions (>2.23), git restore and git restore --staged are the preferred ways to discard changes in the working tree (git checkout -- .) and staged changes (git reset --) respectively.

My point today is that, if we wish to count lines of code, we should not regard them as “lines produced” but as “lines spent”: the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger.

——On the cruelty of really teaching computing science - E.W. Djikstra

If you are looking at learning CS in a more holistic manner, there’s Path to a free self-taught education in Computer Science!. It’s a list of courses, categorized by topics, which are exactly what a CS undergraduate would learn. It might feel daunting at first, but you can pick any interesting topic and dive in.

I especially recommend CS50P for beginners.

One problem with exceptions is composability.

You have to rely on good and up-to-date documentation or you have to dig into the source code to figure out what exceptions are possible. For a lot of third party dependencies (which constitute a huge part of modern software), both can be missing.

Error type is a mitigation, but you are free to e.g. panic in Rust if you think the error is unrecoverable.

A third option is to have effect types like Koka, so that all possible exceptions (or effects) can be checked at type level. A similar approach can be observed in practical (read: non-academic) languages like Zig. It remains to be seen whether this style can be adopted by the mainstream.

Black Panther the movie actually borrowed some art elements from Afrofuturism. Although it’s not very pronounced.

In general, given a Turing machine which outputs the result of a procedure to its memory tape, you can equivalently construct a recognizer of valid input/output pairs. Say P is the procedure, then the recognizer R is let (i, o) = input in P(i) = o

The reverse is also possible. Give a recognizer R, you can construct a procedure P that given part of the input (can be empty), computes the rest of the input that makes R accept the whole. It can be defined as for o in all-strings, if R(i, o) then output o and halt, else continue.

It might feel contrived at first, but both views can be useful depending on the situation. You’ll get used to it soon with some exercises.

For all possible input, only recognize the one input that’s (under certain encoding scheme) equal to the sum of the given list. That’s for a given list.

Another more general approach is that, only recognize the input if (under certain encoding), it’s a pair of a list and a number, where the number is the sum of the list.

Look, there’s a thing called safety-catch and that’s why my son can play with semi-auto rifles.

No, the inventor Chatty Grandparent will never let that happen.

IMHO the reality is more complicated than what’s described here.

1. Open source is sustainable (in the sense that people will continue to do it), even without the maintainers getting paid, for better or worse. This is evidenced by the history and the majority of open source projects now.

2. The bait-and-switch problem, which gets the maintainers paid, hurts the ecosystem in the long run, which relies heavily on the good faith.