When you write tutorials on Dev.to (or GitHub, or anywhere else) your workflow is probably repetitive. Maybe it looks something like this:
- Create the full app
- Break the app into code samples
- Awkwardly arrange the code samples in order
- Follow along yourself
- Realize the code samples don't make sense
- Make a ton of edits
- Write explanations for each code sample
- Do everything again for a video
You end up repeating your work and explaining yourself over and over; in this case, at least 3 times. If something needs to be updated, well, start all over.
That's why I created Paircast. I spent 6 years in Developer Relations writing tutorials. I dreamt of a better way, then I built it.
Paircast squashes all these steps into a single process.
As you work, Paircast records your screen, microphone, and camera like a screencast or live-coding on Twitch.
Now I know what you're thinking. Video sucks for coding. You can't search, you can't copy and paste, and it's hard not to navigate.
Paircast uses git behind the scenes to track file changes and align them with your screencast. Code changed are displayed as git diffs within a markdown file next to your video. See a demo here.
Not only that, but Paircast transcribes your voice and weaves what you say between the code changes.
And what about git?
Paircast actually links commits back to the video as well. So when you upload your full example to GitHub or GitLab, developers can jump to the point in the video where that line of code was created!
Check out the docs on using git blame with Paircast for more on that.
Ready to get started!? Awesome. Paircast is available for Mac and Windows, and it works with any programming language.
Paircast is currently in beta, but you can get instant access just by joining our Discord. Stop in, say hi, talk to our #beta bot, and let me know how things go.
It doesn't stop here. I designed Paircast to be "screencasts for developers," and the use cases go far beyond tutorials. You can use Paircast for:
- Creating onboarding guides
- Answering support emails
- Interviewing developers with coding takehomes
- Video Pull Requests
- Performing code review
- Conducting developer experience research
I've got a lot of writing to do! Follow Paircast here on Dev.to to follow the Paircast journey.
Posted on by: