Yes, I don't recommend any live coding in your first one. No reason to add one more thing to be nervous about. And I've seen Sarah's recordings, they work great for talks! She can describe what's going on without having to type at the same time.
Which I'm not implying Sarah couldn't do that, she totally could! Just that I've seen her walk through code and point stuff out because it was playing instead of having to code it and hope YOU the audience are following the right parts. 😁
^ this, also less points of failure make you more sure of yourself.
It's about your audience and communicating with them, not showing off, so if you can prepare ahead of time, you can deliver a lot of content that won't fail instead of a small amount that might
A middle ground between live coding and not is: gitcrawl https://github.com/magnusstahre/git-stuff/blob/master/README.md… You make multiple commits ahead of time, each at a stage of development, then during your talk, with one command, you can go to the next commit and the next ...