I create the article on Hashnode, taking the pictures of the Demo and expanding the steps one by one
8. Voiceover
To record the Voiceover, which is basically me playing the video and explaining what is going on, I use @getaudacity
9. Edit VoiceOver
The Hardest Part!
I align the Demo with the voiceover and the final result is pretty clean, but it takes a lot
10. Add Animations/Blur
I add animations between scenes and if necessary blur things we don't want to show in the video, such as passwords and private keys. this sometimes takes longer to edit the video itself!
11. Body Render
when I quality level I like, I create a video for what I call the "body", which is the central part of the video, basically, the demo+voiceover properly cut
When I reach this moment I am happy because this is the toughest part.
12. Body Check
I check that the video is of good quality and that there are no errors,
in case there are errors:
- I correct them
- I render it again
- I check it again
all the rendered bodies are versioned, so I can check previous versions in case something wrong happens
To do that, I use @canva. I have the pro version and it's worth the money.
14. Record Outro
I prepare what to say at the end of the video.
Usually, it's just a goodbye but sometimes I try to add something, an expression, or a Call to Action ("write a comment below, what do you think,...") also related to the specific video
and of course I rem to sub!
15. Record Intro
I add a catchy intro.
A Style I like is to use a slightly different version of the thumbnail and explain things just pointing them on my back!
Of course, to do this I use a Green Screen. I have the @elgato one which is a lifesaver.
16. Edit Intro
I put both the intro and the outro in Da Vinci Resolve
Usually, I record the outro first because it's easier, but I edit the intro first. I cut the parts I don't like (not too many cuts btw, and in case I record it again)
17. Edit Outro
Usually, it's not super hard but it takes a while.
I also add some transitions between the central body and the final part.
The final video is almost ready at this point.
18. Add Chapters and note
I add some simple texts.
These will become the chapters on the YouTube Video
I write them down so later I will add them to the youtube video (not necessary if the video is not very long)
19. Final Render
I check the video settings and I render the final video.
I usually use the .mp4 extension and HD, sometimes I go for 4k (probably overkill for tutorials)
20. Check Final Video 🍿
I grab some popcorns and I check the final version!
I love this part but sometimes it's like..."ahhhh i have to render it again!"
21. We are not done yet! (but almost)
I put the video on YouTube and I wait for the HD version to get uploaded.
Then I add:
- Title
- Description
- Tags
- Chapters
- Subtitles
- Add the playlist, set End Screen and Cards for the video
22. Article Review
After this, I create the final version of the article, just reading it again and fixing what I don't like/change
I link the article to the video and the video to the article, and both of them to the Github repository.
23. Prepare the Promo and publish
We are almost there! I prepare the promo for:
- Twitter
- Linkedin
- Instagram
- @ShowwcaseHQ
Then I publish and put the promo out.
Done ✅
• • •
Missing some Tweet in this thread? You can try to
force a refresh
It's the standard way to interact with contracts in the Ethereum ecosystem:
- from outside the blockchain
- for contract-to-contract interaction
Data is encoded according to its type.
The encoding requires a schema to decode
Assumptions
Assumptions for contracts:
- interface functions are strongly typed, known at compilation time, static
- they'll have interface definitions of contracts they call available at compile-time
This is not for contracts with:
- dynamic interface
- only known at run-time