tl;dr:(1) Ask yes / no questions to check your understanding quickly. (2) State your current understanding. (3) Be willing to interrupt. (4) Don’t accept responses that don’t answer your question. (5) Take a minute to think, especially if you're surprised by an answer and need time for a new question.
tl;dr:"I’ll start out by talking about a “backwards” approach to learning that I think a lot of you will recognize (do projects first without fully understanding what you’re doing, fill in missing knowledge after), and then talk about I try to teach in a way that works better with that mode of learning."
tl;dr:Start with real code that you wrote and then "remove irrelevant details to make it into a self-contained example, instead of coming up with examples out of thin air." Julia runs through two types of examples - (1) realistic examples that sell the concept and (2) surprising examples that change someone's mental model.
tl;dr:Julia outlines 5 reasons why bugs might feel impossible to solve, each of which is explained in detail: (1) The bug is hard to reproduce. (2) You don’t understand the overall system well. (3) It’s hard to get data about the bug. (4) One of your assumptions is wrong. (5) The bug is really complex.
tl;dr:Julia outlines things your manager may not know and how to "manage them up", including what’s slowing the team down, what individual people on the team are working on, where the technical debt is, and more.