How to egghead

Show First, then Maybe Explain

Key Takeaways

  • Start writing code while talking about it, then see if any additional explanation is required
  • Remove extra information that would take away from what you're teaching (refer to Screen Setup Feedback Cycles for more information).

This feedback cycle for “show, don’t tell” and removing distractions is Error handling with the JavaScript Array#some method by Domitrius Clark

First Take


Starting off, I love how clear his voice is. He also moves his cursor to “follow the action” across the screen, which is helpful for the learner. But immediately, I can also see that there’s a lot of clutter on the screen from his desktop, browser, bookmark, etc. And there’s a long introduction, where he’s just speaking, rather than showing/doing.

Let’s see what the official first take feedback was!

First Take Feedback


  • START-00:19 - This can be cut as it’s an introduction. Great information but this type of info would be present in the lesson description as it builds context for what you’re about to do.
  • 00:20- How you start here is what we’re looking for.
  • 01:11 - Here is where you would want to give a walk through/review of what is happening in the data from the function call to the output on the screen.

Screen Setup

Screen Setup Image

Second Take


There’s a little less clutter, and the black bands to the sides are gone, but we can probably reduce clutter even more by using a browser as “new user” or incognito mode, and also getting rid of the task bar at the top.

But he’s getting right to the point, and types while speaking, as well as continuing to use the cursor to navigate the learner’s gaze.