tl;dr: A "litmus test for effective leadership: any room that you enter should have more certainty and a firmer plan by the time that you leave it." A tactical list of how to achieve this - have measurable outcomes, use documents for complex decisions, and more.
tl;dr: Each test should (1) test one thing (2) use precisely the data it needs (3) be disconnected from other tests (4) provide context to find the problem in error messages.
tl;dr: "The tradeoff between the computational power of a language and the ability to determine what a program in that language is doing." Built-in array functions like .map & .filter may seem powerful but reduce flexibility. Jesse recommends custom code for readability and error reduction.
tl;dr: "One pattern I’ve noticed in myself is the need to perform perfectly. And if I am learning, which necessitates doing something poorly, then I think there is something wrong with me." Sarah outlines the 3 states and how they help her through this.
“I’ve finally learned what ‘upward compatible’ means.
It means we get to keep all our old mistakes.”
tl;dr: A small number of companies manage a large portion of the internet's infrastructure. This trends towards a single point of failure and places greater power in the hands of a few.
tl;dr: "Almost complete answers to "Front-end Job Interview Questions" which you can use to interview potential candidates, test yourself or completely ignore."
tl;dr: “We find that GPT-3 can generate samples of news articles which human evaluators have difficulty distinguishing from articles written by humans.”