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.
tl;dr:"I’ve been writing some comics about CSS this past week, and I thought as an experiment I’d post them to my blog instead of only putting them on Twitter."
tl;dr:Given candidates won't know your interview process from the start - which can lead to confusion - share a simple document beforehand outlining the process and how they should prepare. Julia provides Stripe's sample document.
tl;dr:Julia's goal is "to be able to write little websites with less than 200 lines of Javascript that mostly work." She runs through what all she's been able to do playing around with simple JS and without using a framework.
tl;dr:Julia started to believe that it was impossible to understand basic CSS concepts, impeding her own ability to learn. After shifting her attitude, she saw a major difference in her ability to learn.