You’re quite welcome! Usually for a video like this it’s at least a month or two in the making… though in the last two weeks leading up to the release it’s more of a flurry of activity as I start working on things beyond “does it boot” and “why does it exist”.
I generally start with an idea / concept that I think will be interesting to other people (in this particular case, it’s “a lot of us want an awesome Arm desktop for Linux… and you basically just have Apple right now, but Asahi is not a first-class experience. Could this machine give us that?”
But to make it more clickable I decided to focus the intro bit on ‘Could this be the next Mac Pro’? (needs to be slightly clickbaity to get people to actually click. All of us engineering types SAY that we don’t like clickbait, but for 99% of us, if you gave us the clickbait version and the non-clickbait version in your YouTube feed… we’d click the clickbait version 100% of the time 
But the script gets started with a rough outline and notes about 2 weeks prior to filming. I generally have 5-6 videos in that state at any given time.
Then I choose to put a video on the schedule, and then it’s either top priority (and I work 6-8 hours daily on getting the testing I need done) or it’s 2nd priority (if I have blocking issues or open questions that need resolution to get further).
But about 1 week out, I start finishing up the script, usually cutting some of the juicy details we programming/engineering nerds love but parts that cause 90% of the other viewers to click off the video. Sadly, if I don’t do that, YouTube severely cuts down on the video’s reach (so a narrow but deep audience). I tend to give the depth in my GitHub issues, bug reports, Twitter, and my blog, and focus on highlights on YouTube, where it affects my bottom line!
Then 3-4 days before posting, I record my script, and start the editing process. Generally from here it takes 1-2 hours per minute of video, but some videos can take 3-4 hours per minute.
Someday I’ll maybe have an editor, who can help with this, because it eats into the time I can spend doing benchmarking, testing oddities, trying to break (and fix) things, etc.
Finally, on the day of posting a video, I generally take the morning to watch comments, hop on Twitter/Mastodon/elsewhere to see what’s happening, and then start ramping up in the afternoon on the next video. It’s a grind, but it’s similar to the grind you’d have shipping features for software, so it’s a familiar grind!
If i can channel my inner Clarkson.
