YouTube for Developer Relations
YouTube is the second-largest search engine and where developers go to learn. This skill covers tutorial structure, screen recording setup, live coding, shorts vs long-form, thumbnails, and SEO for technical content.
Before You Start
- Read
.agents/developer-audience-context.md if it exists
- Audit existing technical YouTube channels in your space
- Understand: Developer YouTube is a long game — consistency > perfection
Understanding Developer YouTube
Who Watches Dev Content
| Audience | What they want | Video length |
|---|
| Learning developers | Complete tutorials | 15-45 min |
| Working developers | Quick solutions | 5-15 min |
| Senior developers | Deep dives, architecture | 30-60 min |
| Decision makers | Demos, overviews | 3-10 min |
| Conference attendees | Recorded talks | 20-45 min |
Content Types That Work
| Content type | View potential | Effort | Notes |
|---|
| Tutorial (build X) | Very high | High | Evergreen traffic |
| Problem/solution | High | Medium | Search-driven |
| Tool comparisons | High | Medium | High search volume |
| Live coding | Medium-high | Low | Engagement-focused |
| Project updates | Medium | Low | Community building |
| Conference talks | Medium | Low | Repurpose content |
| Shorts | High reach | Low | Discovery-focused |
Successful Dev YouTube Channels
| Channel | Style | Why it works |
|---|
| Fireship | Fast, dense, opinionated | Respects viewer time |
| ThePrimeagen | Personality, live reactions | Authentic, entertaining |
| Traversy Media | Clear, beginner-friendly | Comprehensive tutorials |
| Hussein Nasser | Deep dives, whiteboard | Engineering depth |
| Ben Awad | Casual, real coding | Relatable, genuine |
Tutorial Structure
The Tutorial Template
Opening Hook (First 30 Seconds)
| Element | Purpose |
|---|
| Show the end result | Prove it's worth watching |
| State what they'll learn | Set expectations |
| Mention prerequisites | Qualify viewers |
| Estimated time | Respect their time |
Example hook:
Pacing Guidelines
| Video length | Segment length | Notes |
|---|
| 5-10 min | 1-2 min segments | Fast, focused |
| 15-30 min | 3-5 min segments | Standard tutorial |
| 30-60 min | 5-10 min segments | Deep dive |
Common Tutorial Mistakes
| Mistake | Impact | Fix |
|---|
| Too much setup | Viewers drop off | Skip to interesting parts |
| Not showing end result | No motivation | Show finished product first |
| Going too fast | Confusion | Pause on key steps |
| Going too slow | Boredom | Edit out pauses, typos |
| No timestamps | Poor navigation | Add chapters |
| Walls of code | Overwhelming | Build incrementally |
Screen Recording Setup
Essential Equipment
| Equipment | Budget option | Better option |
|---|
| Microphone | Blue Snowball ($50) | Shure SM7B ($400) |
| Screen recording | OBS (free) | ScreenFlow ($170) |
| Webcam | Built-in | Logitech C920 ($80) |
| Lighting | Window light | Ring light ($30) |
| Editor | DaVinci Resolve (free) | Premiere Pro ($22/mo) |
Audio is More Important Than Video
| Priority | Why |
|---|
| 1. Clear audio | Bad audio = immediate click away |
| 2. Readable code | Text must be crisp |
| 3. Good lighting | For facecam sections |
| 4. High resolution | 1080p minimum |
Screen Recording Best Practices
| Setting | Recommendation |
|---|
| Resolution | 1920x1080 or 2560x1440 |
| Font size | 18-24pt in editor |
| Theme | Dark theme (easier on eyes) |
| Zoom | Use IDE zoom for key sections |
| Notifications | Disable all |
| Browser | Use clean profile, no bookmarks bar |
Recording Workflow
- Script key points (don't read verbatim)
- Test audio levels before recording
- Record in segments (easier editing)
- Leave pauses for edits (clap or say "edit")
- Show face at transitions (builds connection)
- Record extra b-roll (diagrams, browser, terminal)
Live Coding Content
| Format | Length | Platform |
|---|
| Twitch stream → YouTube | 1-4 hours | Both |
| YouTube Live | 30-90 min | YouTube |
| Pre-recorded "live" | 20-45 min | YouTube |
Live Coding Best Practices
| Do | Don't |
|---|
| Explain your thinking | Code silently |
| Embrace mistakes | Pretend you know everything |
| Read chat | Ignore audience |
| Have a goal | Meander aimlessly |
| Take breaks | Marathon without pause |
| Use timestamps post-stream | Leave as giant blob |
Common Live Coding Content
| Content | Example |
|---|
| Project from scratch | "Building a REST API live" |
| Code review | "Reviewing subscriber PRs" |
| Problem solving | "LeetCode medium problems" |
| Exploring new tech | "Learning Rust in public" |
| Bug hunting | "Fixing production issues live" |
YouTube Shorts (< 60 seconds)
| Aspect | Best practice |
|---|
| Hook | Immediate (first 1-2 seconds) |
| Length | 30-45 seconds optimal |
| Aspect ratio | 9:16 (vertical) |
| Content | One tip, one concept |
| Text | Big, on-screen captions |
| Audio | Clear voiceover |
Shorts Content Ideas
| Type | Example |
|---|
| Quick tips | "One command to speed up Git" |
| Syntax shortcuts | "JavaScript spread operator in 30s" |
| Tool demos | "VS Code extension you need" |
| Code transformations | "Before/after refactoring" |
| Hot takes | "Stop using X, here's why" |
Shorts Strategy
| Goal | Approach |
|---|
| Grow subscribers | Post 3-5 shorts/week |
| Drive to long-form | Tease tutorials in shorts |
| Algorithm favor | Consistent posting schedule |
| Repurpose content | Cut from long videos |
| Long-form | Shorts |
|---|
| Search traffic | Discovery traffic |
| Watch time revenue | Low revenue |
| Depth | Breadth |
| Subscribers who stay | Subscribers who scroll |
| Comments, community | Less engagement |
Thumbnails for Developers
Thumbnail Principles
| Element | Guideline |
|---|
| Text | 3-5 words max |
| Face | Expression adds emotion |
| Logo/icon | Tech being discussed |
| Colors | High contrast, brand consistent |
| Composition | Rule of thirds |
Thumbnail Patterns That Work
| Pattern | Example |
|---|
| Face + tech logo + emotion | [Surprised face] + [React logo] + "It changed everything" |
| Before/after | [Broken code] → [Working code] |
| Big text + icon | "STOP" + [X mark] |
| Comparison | [Tech A] vs [Tech B] |
| Result preview | [Screenshot of finished app] |
Thumbnail Creation
| Tool | Best for |
|---|
| Canva | Quick, easy templates |
| Figma | Design control |
| Photoshop | Advanced editing |
| Thumbnail templates | Consistency |
A/B Test Thumbnails
YouTube allows thumbnail testing:
- Upload video with thumbnail A
- After 48 hours, change to B
- Compare CTR in analytics
- Keep winner
YouTube SEO
Where Keywords Matter
| Location | Impact | Best practice |
|---|
| Title | Highest | Primary keyword early |
| Description | High | First 2 sentences keyword-rich |
| Tags | Low | Include, but don't overthink |
| Captions/transcript | Medium | Auto-generated + edit |
| Filename | Low | Include keyword anyway |
| Formula | Example |
|---|
| [Tech] Tutorial: [What you'll build] | "React Tutorial: Build a Todo App from Scratch" |
| How to [Task] with [Tech] | "How to Deploy to AWS with Docker" |
| [Tech A] vs [Tech B]: Which is Better? | "Next.js vs Remix: Which Should You Learn?" |
| [Number] [Topic] Tips in [Time] | "10 VS Code Tips in 10 Minutes" |
| Why I [Action] [Tech] | "Why I Switched from React to Svelte" |
Description Template
Research Keywords
| Tool | Use for |
|---|
| YouTube search autocomplete | Real search queries |
| TubeBuddy/VidIQ | Search volume, competition |
| Google Trends | Trending topics |
| Competitor titles | What's working |
Do's
- Do show the end result first
- Do add chapters/timestamps
- Do use clear, readable code fonts
- Do invest in audio quality
- Do maintain consistent posting schedule
- Do engage with comments
- Do repurpose to shorts
- Do create custom thumbnails
Don'ts
- Don't skip the hook
- Don't use tiny fonts
- Don't record with room echo
- Don't forget CTAs
- Don't post inconsistently
- Don't ignore SEO basics
- Don't make clickbait thumbnails (trust erosion)
- Don't perfectionism (ship it)
Content Calendar
Weekly Schedule Example
| Day | Content |
|---|
| Monday | Shorts (tip/trick) |
| Wednesday | Long-form tutorial |
| Friday | Shorts (from Wednesday video) |
| Weekend | Edit next week's content |
Monthly Planning
| Week | Focus |
|---|
| Week 1 | Tutorial (main content) |
| Week 2 | Live stream or Q&A |
| Week 3 | Tutorial (main content) |
| Week 4 | Comparison or review |
| Tool | Use case |
|---|
| Octolens | Monitor YouTube and social for mentions of your tech topics, competitors, and find what developers are asking about. |
| OBS Studio | Free screen recording and streaming |
| ScreenFlow | Mac recording and editing |
| DaVinci Resolve | Free professional editing |
| Descript | Edit video by editing transcript |
| Canva | Thumbnail creation |
| TubeBuddy | YouTube SEO tools |
| Riverside.fm | Remote recording |
Getting Started Checklist
First video:
developer-audience-context — Know who's watchingdev-to-hashnode — Turn videos into blog postslinkedin-technical — Share videos on LinkedInx-devs — Promote videos on Twittergithub-presence — Link repos in descriptions