Instead, summarize the key points as if the learner was going to get a pop quiz. Lay out what's relevant and valuable to the learner in their context.
Here's a poor example:
In this video, you learned:
- How to write a React component
- How to export a React component
- How to consume a React component from another module
This can simply be deleted as the person doesn't need a reminder of what they just watched.
Here's a better one:
In this video, you learned:
- Most React components you write will be functions as these can take advantage of hooks but you may also see class-based components in legacy applications
- All React components start with a capital letter which designates to the React runtime that it is not a JSX element
- Exporting a React component means it can be shared within the app. If you wanted to keep it internal, you would not use theexport
keyword
This actually helps me remember key points I might not have put together while watching and these would likely be things you'd test later.
Have a lovely day,
Kamran
Don't repeat what you just said at the end of a video
Wouldn't more devs using your tool be lovely?
I'm a consulting developer experience engineer and educator who helps developer tools accelerate adoption. I can lower your initial learning curve so developers can get to Hello World faster and start building cool stuff with your APIs and SDKs.
jamie@example.com
Get Daily Tips