What I learned from my first screencast
Tags: beginners
Published: 2021-04-02 13:26:33

I recently recorded my first screencast and, wow, I have a lot of things to improve on. The video itself is 6 minutes long, but it took around 3 hours to record. I don’t know how long recordings usually take, but I’m pretty sure that’s too long! I also recorded two versions of the screencast, which didn’t help with the time. In one version, I recorded myself talking and coding at the same time. And the other I recorded the audio and video separately. In this post, I’ll talk about the lessons and mistakes I made during this process.

## Lessons Learned
### Recording process
What helped me in the second attempt was separating recording the video and the audio. I got this idea from Jeff Delaney, who did a video explaining [how he records screencasts](https://www.youtube.com/watch?v=N6-Q2dgodLs&list=WL&index=1 "How Jeff Delaney records screencasts"). Separating the video and audio made my life a whole lot easier. I’m really bad at multitasking, so trying to record myself coding, talking, and thinking about the next steps was a recipe for disaster. I wasn’t able to focus properly, and I struggled to get words out. Props to live streamers or those who record with both audio and video. It’s really hard! 

When recording audio, my tip is to record a few lines at a time. Recording in chunks makes it easy to recover from mistakes. Also, repeat the last line when you’re moving to the next set of lines. Repeating the last line means you keep your intonations consistent. And stops that pesky unexpected-breathing-in-between words problem!

Finally, I had a hard time syncing the video recording with the audio. There were points in the audio where I was jumping back and forth between code blocks. This jumping resulted in furious scrolling and hurriedly highlighting the right piece of code. Improving this flow has a lot to do with planning. It’s something that I want to keep in mind for next time.

### Properly outlining
I wrote my outline with a focus on key ideas. This gave me the freedom to expand on an idea, or play around with the sentence when recording. I make less mistakes this way, because you can’t make a mistake if you’re not following a script. But I needed to flesh out this outline a little more.

Something that I hate when watching other screencasts is hard cuts where you’re teleporting across the screen. And during my planning I never accounted for any of these cuts. Next time I do a screencast, I want to detail the transitions. I’d like to note down the files I want to show, specific code blocks, and the information I want to convey during those code blocks. 

## Incremental improvements
I’m happy with the result of the screencast. There’s more that I could’ve done but it’s all about incremental improvements! I’m never going to have a perfect video, and that’s a good thing. I’m glad that I have things to improve on and I’m excited to work on the next video. If you wanted to give it a watch, here’s a link to my first screencast, [Feeling at home with the Phoenix framework](https://www.youtube.com/watch?v=tO5M8QQ9vzs&t=54s "Feeling at home with the Phoenix Framework: from Rails to Phoenix").

{% youtube tO5M8QQ9vzs %}

---

Photo by <a href="https://unsplash.com/@claytonrobbins?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText">Clayton Robbins</a> on <a href="https://unsplash.com/s/photos/process?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText">Unsplash</a>