Short answer: developers watch short videos that teach something real: a terminal trick, a bug and its fix, a quick benchmark you ran yourself, or a "build this in 60 seconds" with real code. Keep marketing language out, show the code on screen at readable size, and let an engineer present. Link to docs and a free tier rather than a sales page.
What developer audiences respond to
| Works | Doesn't |
|---|---|
| Real code, readable on a phone | Stock footage and buzzwords |
| An engineer explaining | A voice actor reading a feature list |
| A problem developers recognize | Abstract "digital transformation" |
| Honest tradeoffs | Claims without a way to check |
| A link to docs or a quickstart | "Book a demo" |
Formats for dev tools
| Format | Example (made-up) | Notes |
|---|---|---|
| Terminal trick | "One flag that makes your logs readable" | Big font, dark theme |
| Bug and fix | "Why this query was slow" | Show before and after |
| Build in 60 seconds | "An API endpoint with auth" | Speed up typing, keep it real |
| Benchmark you ran | "Cold start, our way vs default" | Publish method and code |
| Code review | "Three problems in this snippet" | Use your own or permitted code |
| Release note | "What changed in v2.3" | One change per clip |
| Explainers | "What an MCP server actually is" | Diagrams or slides |
When you show benchmark numbers, publish how you measured them, so anyone can repeat the test.
Making code readable
- Editor font size 20–24 pt, a high-contrast theme.
- Show only the lines that matter; fold the rest.
- Record a narrow editor window so the vertical crop keeps the text large.
- Burn in captions for the spoken explanation.
The Mac side is covered in screen recording setup.
Who should make the videos
The best developer videos usually come from the engineers who built the feature, with a marketer handling editing, captions and posting. Keep the engineer's time small: a 20-minute recording session per week can produce several clips. Give them a short template (problem, code, result) so they do not have to think about video structure. Credit them by name if they want it.
Which platform
YouTube is often the natural home for developer content because tutorials live there, and Shorts can point to the full tutorial with a related video link (YouTube Help, checked 17 September 2026). TikTok and Reels can reach developers too, especially for quick tips and humor. Test before committing; see YouTube Shorts for SaaS and does TikTok work for B2B SaaS.
A four-week starter plan
Week one: three terminal or editor tricks. Week two: two bug-and-fix clips and one release note. Week three: one "build in 60 seconds" and two explainers. Week four: repeat the format that held attention best, and answer the best comment questions on video. Treat the plan as an assumption to adjust, not a formula.
Measuring without being annoying
Developers dislike tracking-heavy links. A clean docs URL with standard UTM parameters on the profile link, plus a "where did you hear about us" field at signup, is usually enough. Google Analytics recommends source, medium and campaign on every tagged URL (Google Analytics Help). See UTM links.
Developer tools and agents
Many dev-tool teams already use AI agents. Farmero's local MCP server
(farmeroctl mcp) lets an MCP client check the fleet and queue posts for
iPhones driven by your Mac, while publishing stays behind a switch you
control. It is a practical example to show, too. See
posting with MCP.
FAQ
Do developers really watch TikTok?
Some do. Test with a few weeks of tips before committing a team.
Should the presenter be an engineer?
Where possible, yes. Developers trust people who clearly write code.
How technical can a short video be?
Quite technical, if it stays on one idea and the code is readable.
Where should the link go?
To docs, a quickstart or a free tier, tagged with UTM parameters.