Fast F#: Intro to Options 

The reason null is called a billion dollar mistake, is not that it is a bad idea by itself, but rather that it causes a lot of developers and code to fall into a pit of failure rather than a pit of success. Option types make that pit a pit of success instead (as Scott Wlaschin likes to say), since this is explicit. It's definitely more important to consider this for more high level languages than the low level ones. Low level languages have the benefit of having a quite limited feature set and quite little abstraction, forcing you to think things through (but slowing down your development velocity, generally speaking). In high level languages, abstractions need to be intuitive or encoded, especially as the code base grows larger and more complex. It's very interesting that this kind of thing is built into a language like Rust now. I think it's a cool notion, and I'm sure we'll be seeing less nulls in the future in general just because it's harder to reason about than many would like in a growing system.

Not that I noticed it in this video (or other videos), but if you are on Windows, there is a pretty cool tool you can use if you have a powerful GPU on your computer, for extremely powerful noise reduction called Nvidia Broadcast. So if you have to record on a noisy day, and you're on Windows, and you have one of their supported GPUs, it's a powerful (free) tool to help make that less of a problem.

Null was pronounced "a billion dollars mistake" not by "some people" but by Anthony Hoare, the "creator" of the "null" himself, in his "public apology". In which he said that "null" should never been implemented, and that it was implemented not because "it made sense in some contexts" or had another "big idea" behind it, but "because it was easy to implement" :) He also said that he had no idea that anyone would ever use it.

I like the way it's implemented as an explicit type. It would be nice if eventually it had an overloaded syntax to allow something like "let cValue = aValue + Some 1" and also knowing that "let dValue = aValue + emptyValue" would make no sense.

I think you still need to add some tags to your videos, if you want better reach. Especially if you want to reach people who might not have looked at F Sharp before (probably your target audience with this series).

Option.bind would be a good follow up, Even more I hope you go over collections functions like tryFind tryHead tryTail choose Avoiding null reference exceptions gets all the spotlight but to be honest it's these patterns/functions that Option enables that I miss most going back to null.