/Julia Evans

How To Get Useful Answers To Your Questions 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.

featured in #263

Tools To Explore BGP tl;dr: After the FB outage last week, Julia wanted to explored BGP and shares 5 tools that are helpful to learn more about the protocol, listed here.

featured in #259

Teaching By Filling In Knowledge Gaps 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."

featured in #256

Quadratic Algorithms Are Slow (And Hashmaps Are Fast) tl;dr: Julia guides us through what a quadratic time function looks like, why it's slow, how to convert a quadratic algorithm into a linear one using a hashmap.

featured in #252

Write Good Examples By Starting With Real Code 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.

featured in #236

Reasons Why Bugs Might Feel "Impossible" 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.

featured in #233

Things Your Manager Might Not Know 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.

featured in #226

What To Talk About In 1-1s tl;dr: You should talk about what's going well, what's not going well, team priorities, and 3 other things sketched out for you in this post.

featured in #203

Some CSS Comics 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."

featured in #198

When Your Coworker Does Great Work, Tell Their Manager tl;dr: Ask if it's ok first - since there are scenarios it may be counterproductive. Think about when it's important, how to do it, and other guidance.

featured in #193