Avoid Intros and Outros
Any information you would want to put into an Intro or Outro belongs in the accompanying description, title, course page, etc. The lesson is only for showing the process. Talking about yourself, the lesson, or other lessons is a waste of time.
[00:00] Avoid introductions like, "Hey everybody, John Lindquist again from Egghead.io," or even, "Let's look at how to add RxJS to View." Instead, just start doing it.
[00:11] Install your packages. Import the module. Type out the required code to use it. Leave the description or introduction down in the description of the lesson. If they need an introduction they can read that.
[00:25] Then, at the end of your lesson avoid saying, "Goodbye," or, "In the next lesson we'll explore how to do X, Y, and Z." Instead, the next lesson will show up in a playlist or, if it's part of a course, it will automatically play.
[00:40] So there's absolutely no reason to say, "In the next lesson we'll cover X, Y, and Z," if that next lesson will start and a title of, "How to do X, Y, and Z," pops up then they're already there. It's all about respecting your audience and not wasting their time.
Member comments are a way for members to communicate, interact, and ask questions about a lesson.
The instructor or someone from the community might respond to your question Here are a few basic guidelines to commenting on egghead.io
Be on-Topic
Comments are for discussing a lesson. If you're having a general issue with the website functionality, please contact us at support@egghead.io.
Avoid meta-discussion
Code Problems?
Should be accompanied by code! Codesandbox or Stackblitz provide a way to share code and discuss it in context
Details and Context
Vague question? Vague answer. Any details and context you can provide will lure more interesting answers!