How to Read Code While Recording a Coding Tutorial
· 6 min read
Coding tutorials are hard to record because you are doing three things at once: talking to the viewer, remembering what comes next, and typing code without mistakes. A script solves the first two — if you can see the words and the code clearly while you record.
Write the script around the code, not the other way round
Start from the code you want to end up with, then split it into the steps a viewer can follow. For each step, write one or two sentences that say why the code exists before you show what it is. Viewers forgive slow typing; they don’t forgive not knowing why.
Keep spoken sentences short. Long sentences that look fine on paper make you run out of breath on camera.
- One idea per step: “add state”, “handle the click”, “show the result”.
- Say the file name and the line you are editing before you type.
- Put the exact code for each step right under the sentence that introduces it.
Keep code readable on the prompter
Most teleprompters treat everything as prose: indentation collapses, braces wrap onto new lines, and a ten-line function turns into an unreadable paragraph. That is when people look away from the camera to check their editor.
Use a prompter that keeps code as code — monospaced, indented and ideally colored — so a glance is enough to see what to type next. In TeexFlow, code you paste from your editor becomes a framed, syntax-highlighted block, and the sentences around it stay normal text.
Place the prompter where your eyes already are
For screen-recorded tutorials with a face cam, put the prompter window directly under the webcam, as narrow as you can read comfortably. Your eyes then move only a few degrees between the lens and the text.
If you film with a separate camera, use a tablet or second monitor right below or behind the lens, or a beam-splitter teleprompter with the text mirrored.
Control the prompter without leaving the keyboard
Your hands are busy typing, so scrolling the script by hand breaks the flow. Two options work well:
- A phone as the remote: play, pause and change speed with your thumb between typing bursts.
- Voice follow: the prompter listens and keeps up with what you say. A good one skips code blocks, since you type those rather than read them aloud.
Record in short takes
Record one step at a time and keep a clean pause before and after each. If you stumble, stop, take a breath and redo the step from its first sentence — the pauses make the edit easy.
Finally, run the finished code before you publish. Nothing costs a tutorial more trust than code that doesn’t work.