ndand

There is a way to watch the video anyways, on YT with just 2 clicks.

> Valued = useful + hard to find.

I agree, but I think it slightly differently, Valued = useful + hard to replace.

How difficult is to be replaced by some other human or a machine.

I understand it differently,

LLMs predict distributions, not specific tokens. Then an algorithm, like beam search, is used to select the tokens.

So, the LLM predicts somethings like, 1. ["a", "an", ...] 2. ["astronomer", "cosmologist", ...],

where "an astronomer" is selected as the most likely result.

You can capitalize a string in Python using functional style

  ' '.join(map(str.capitalize, string.split(' ')))

which is similar to the example in Ruby, except the operations are written in reverse order.

> I believe there's now also a VS code plugin for the same behavior, but I don't know what it's called.

It's called "sticky scroll". It's a relatively new feature of VS Code.

Not for the rest of their lives. 50 people can live on $100k/year for 20 years.

I used to think commits as snapshots, but it was confusing. Then I read "Git Internals".

A commit contain the "whole" content of each file that we've commited. But since a commit has a pointer to a root commit, it also represents a working directory. Even though a commit contain "whole" files, the git internally stores only parts of the files as an optimization.

When we diff two commits, we see the difference of the file contents in the corresponding working directories that the commits represent.

The "indirect" variable does not point to a list entry directly, like what "head" and "next" variables do, that's why it's named "indirect".

The comment is correct. The "thing" is the variable that holds the "entry". The entry is removed by updating the "thing".

This can't be a satire. It's a guide on how to interview engineers when you're looking for extraordinary engineers, not good or great ones.