The Screencast Experience

Blog Summary: (AI Summaries by Summarizes)
  • The author created a screencast that was published by Pragmatic Programmers.
  • Before starting the project, the author couldn't find any blog posts about the experience of creating a screencast.
  • Creating a screencast is like writing a novella, creating custom graphics per slide, and doing the audiobook for the novella all at once.
  • The author created six 30-minute episodes, starting in February 2012 and publishing on November 7, 2012.
  • The process of creating an episode involved identifying the topic and technologies, creating the slides, writing the manuscript, and doing the voice-over.

You might have heard about my screencast (sample video) that was published by Pragmatic Programmers. Before I started the project, I tried to look around to see if anyone had blogged about their experiences and I couldn’t find one. The closest posts I could find were about writing a book.

These are my thoughts and experiences having written, created the slides, and done the voice-over. I’m hoping that this gives another potential screencaster more information before they embark on their journey.

The Process

Doing a screencast is more like writing a novella, a custom graphic per slide, and doing the audiobook for the novella all at once. This project has six 30-minute episodes. I started it in February 2012 and it was published on November 7, 2012. It was quite a bit of work to bite off.

Creating an episode started with identifying the general topic and technologies I wanted to cover. From there, I created the slides for the episode. Most slides have custom art that I created using Inkscape. Getting the right artwork for each slide took a lot of time. In total, there are 225 slides.

Once the slides were done, I wrote the manuscript. It was a very different mindset than creating the artwork. For the artwork, I was trying to communicate visually. For the manual, I was communicating verbally. I found that they are different enough communication mediums that I tried to separate the two tasks out in to their own time slots. Doing both tasks at the same time just didn’t work well.

Writing each episode required a significant time investment. I faced the same writer’s block when trying to write certain sections. In total, the six episodes have 28,306 words in them. The manuscript was about 10,000 words short of being considered for a novel. Technical book word counts seem to vary quite a bit. I’ve seen some with 90,000 words and some with 40,000 words.

Finally, I did the voice-over. This was another task that didn’t mix with creating artwork or writing. I had to make sure that I was just doing voice-over and nothing else. Creating a good read is surprisingly difficult. I thought it would be closer to my live speaking and it wasn’t. I had a greater fixation on creating the perfect take and a single flub or mess up made me stop the take. This isn’t something you can do live. Doing takes like this also inhibited the flow you can get into while doing a live presentation. There was no room for adlibbing or variations; I had to stick to the manuscript.

Delivering a manuscript well is difficult too. You are basically reading the words you wrote at some point in the past. Simply reading the words isn’t good enough when doing a screencast. You need to give more feeling and intonation to the material. With a live presentation, the audience can see you and watch your facial expression. On a screencast, you don’t have the luxury of your facial expressions and your voice needs to bring that.

My weapons of choice were the Blue Yeti and Screenflow. I highly recommend the Blue Yeti for the screencasts. It did an incredible job filtering out some of the background noise that would have ruined a take. There were times when a leaf blower or pigeon were making noise while doing a take and you can’t hear a thing. The Blue Yeti allowed me to keep working when I thought I would have to stop due to background noise. Screenflow worked well; although their tech support leaves quite a bit to be desired.

Author, Vegetable or Mineral?

I’m faced with an unexpected dilemma now. What do I call myself after this project? Am I an author, a writer, a voice-over artist, or a graphic artist now? I had this conversation with my editor, Jared Richardson. When I tell people what I’ve done, I have a difficult time telling non-technical people what a screencast is. If I had written a book, I could easily tell people I wrote a book. If I had created a movie, I could say I’m a Writer, a Producer or a Director. In some ways, a screencast is a book, movie and art. It’s really this weird hybrid that doesn’t fit well in to a single word.  Jared and I finally settled on Screencast Author. However, this still has the problem of explaining what a screencast is.

Jesse The Salesperson

For the first time in my life, I have a product that I own and directly benefit from. I’ve been a professional Software Engineer for many years and created a lot of products, but I never owned any of them. A sale or lack of sale never directly benefited or hurt me. Now, I have this thing that I can sell and promote that I get royalties on.  A sale directly benefits me and promoting the project directly benefits me. Better yet, I’m making money without having to sit in front of a computer coding. It’s like having your own small business without a lot of the associated costs and problems.

Would I Do It Again?

I think the desire to create another screencast is the best metric for success. The answer, so far, is yes I would create another one. I would do some things different, of course.

My editor, Jared, said that the best business card is a book or screencast. Even early on in my journey, I’ve seen that this is true. Having content at this level really puts you in a different category. Although I’m early on in this phase of my career, my name appears in a list of people who are well on in the teaching phases of their careers. It’s really an honor to have your work appear in a list alongside other luminary works.


Doing a screencast is really about having some unrelated, inter-disciplinary skills. You need to be able to write well, draw/layout well, and speak/voice-over well. I recommend giving it a try because you will learn so much. I really recommend this route to anyone trying to distinguish themselves.

Thanks to my editor, Jared Richardson.

Related Posts