It's usually easier for a non-native English speaker (at least below ILR[1] Level 3 or CEFR[2] Level B) to understand English spoken by another non-native, because the pace is slower, idioms and expressions are not used so regularly, etc. Your accent is much easier for non-natives than a strong Irish accent, for example. So I wouldn't worry about that too much.
[1] https://en.wikipedia.org/wiki/ILR_scale [2] https://en.wikipedia.org/wiki/Common_European_Framework_of_R...
Same goes for a tendency of many native speakers to indulge in idioms, archaic vocabulary and convoluted syntax just for the heck of it. Non-natives just cut to the chase, which is exactly what you want in a technical discussion.
It seems like there are really 2 meta topics: 1: Using C and the OS to maximize performance 2: building distributed systems
That's the reason why in my other comment, the data screencast I created was made in addition to a blog post, where the blog post and the video explicitly link to each other as cross-promotion.
That does extend production time significantly though.
As an aside, I noticed several typos sneaked into comments here and there ('command gets replicated to the salves', etc). I'm half considering filing a pull request for them, but feel it might come across as overly pedantic. Would such a PR be appreciated?
I feel like that knowledge needs to be shared around a bit more.
As a side note, can you share your Terminal color scheme? It's really nice
5. The odd Redis persistence model: fork() and fighting the copy-on-write.
Interesting stuff, I haven't had to write C++ in a few years, it's nice to have a bit of a refresher.
1. Code snippets: show small self contained functions from random places inside Redis.
2. Redis Sentinel: the first design, the immediate redesign of v2, and how it is internally implemented.
3. The use of goto in Redis.
4. Redis protocol parsing and zero-copying of objects.
5. The odd Redis persistence model: fork() and fighting the copy-on-write.
6. Redis crash report. Generation and usefulness over the years.
7. Observability inside Redis: latency hooks, LATENCY DOCTOR and MEMORY DOCTOR.
8. Hybrid data structures: Streams macro nodes implementation.
9. RIO: Redis I/O abstraction and OOP in C.
10. Redis Cluster: how the Redis message bus is implemented.
11. Redis Cluster: hash slots tracking and redirections.
If you have any preference and/or other ideas, will be cool to hear.
About this experience itself, good things: shooting a video takes more or less just the time to record. Preparation is just a few minutes, and later post processing is an automatic process... So in 1 hour max everything is done. However I see that the reach of the videos is very low compared to a blog post, which requires more time to write sometimes, at least to have the same amount of info. So it's a tradeoff. Also consuming the video may be a problem for many, for instance for language barriers due to the speaker accent (in my case) and the listener ability to understand English without subtitles. Let's say I want to make 10 episodes and re-evaluate if it's a good idea to change style and do 5 minutes episodes instead.