Entry 02 · · Engineering team
Not everything deserves a pipeline.
By Emir Alanyalioglu · Updated
I automated the recording, the scripts and the editing of eight training videos. The voice-over I generated by hand: eight clicks. Wiring the API would have taken longer than the clicks.
- 01scriptwritten from the codeagent
- 02recordscreen walkthroughagent
- 03editthe cutagent
- 04voice-overeight clicksby hand
The system
The team I lead turned the codebase of a software product into a training course: eight videos, scripts written from the code, screen recordings and editing produced by a pipeline. One agent reads the code and writes the script, one records the walkthrough, one cuts the video.
Three steps run in the pipeline: script, recording, edit. The fourth step, the voice, I left out of it.
The voice-over I generated by hand. Eight clicks in ElevenLabs.
Wiring the voice API into the pipeline would have taken longer than the eight clicks, and the course will not be re-recorded every week. The pipeline exists for the parts that repeat: the scripts change with every code change, the recording follows the script, the edit follows the recording.
The rule I use: automate the step that repeats and changes, click through the step that repeats and does not. A pipeline is a cost. It has to earn its place.
This is one entry. The rest are in the Lab.