Build-in-Public Strategy

YouTube Shorts for developers who ship

Algorithm mechanics, proven content patterns, and workflows for indie developers documenting the real process.

01 / How It Works

Algorithm Mechanics

Session-based distribution, test pools, and the signals that actually matter for developer content.

Distribution Model

YouTube Shorts are served in infinite scroll sessions, optimizing for session retention — keeping viewers in the feed. Unlike long-form, there's no search discovery. Your video enters the "Shorts Feed" where the algorithm tests it in small pools.

Videos first shown to test pools of 50-500 views. If engagement hits thresholds, distribution scales exponentially.

Key Signals Ranked

Signal Target Weight
Average View Duration 80%+ completion Critical
Loop Rate 15%+ immediate rewatches High
Share/Save Rate 1%+ per impression High
Engagement Velocity 5%+ in first 24hrs Medium
CTR 4-10% from browse Medium

Developer content advantage: Tutorials get higher share/save rates than entertainment. Developers save for later. YouTube treats saves as high-intent signals — more valuable than likes.

Duration Matters

15-22s
Simple Tips
Highest completion rates. Quick hacks, "did you know" content.
25-34s
Mini Tutorials
Sweet spot for problem → solution narratives.
45-58s
Build Breakdowns
Maximum for complex explanations. Risk of drop-off increases.

Avoid 30-44s. The algorithm dead zone — long enough to lose attention, short enough to feel rushed.

02 / Content Models

Proven Patterns

Three models — Fireship, Primeagen, and Build-in-Public — each with different tradeoffs.

The Fireship Model Pattern 01

One concept → One code snippet → Immediate takeaway. Information density + shareability. Developers send these to team chats.

  • Length: 15-25 seconds
  • Posting: 1-3x daily
  • Visual: Screen recording + text overlays, no face
  • Content: Language tricks, hidden features, "did you know"
The Primeagen Model Pattern 02

Strong opinion → Explanation → Call to action. Comment bait through controversy. Hot takes drive 10x more engagement than tutorials.

  • Length: 30-45 seconds
  • Posting: 5-10x weekly
  • Visual: Face-first + screen B-roll, high energy
  • Content: Hot takes, industry commentary, workflow reveals
The Build-in-Public Playbook Your Model

Problem → Build process → Result/Demo. Document the messy middle. Show constraints, tradeoffs, failures. This is the hardest pattern but creates the strongest connection.

  • Length: 25-40 seconds
  • Posting: 1-2x daily
  • Visual: Screen recordings + code + Hermes outputs
  • Content: Feature builds, bug fixes, design iterations, real metrics

03 / Attention Capture

Hook Formulas

First 3 seconds determine 80%+ of performance. Patterns that work for dev content.

1 The Contrarian
[Common practice] is wrong because [specific reason]

"Stop using useEffect for data fetching. Here's why 90% of React devs get this wrong."

2 The Specific Number
I [achieved result] in [time] with [specific thing]

"I shipped 47 app updates in 3 months using this one automation."

3 The Process Reveal
How I [did thing] in [timeframe] — full process

"How I built an iOS widget that tracks coding time — from idea to App Store in 48 hours."

4 The Hot Take
[Strong opinion] — and here's why

"SwiftUI is broken for production apps and Apple won't admit it."

5 The Discovery
I discovered [surprising thing] by [unexpected method]

"I discovered YouTube's algorithm favors this ONE format by analyzing 10,000 dev Shorts."

04 / Templates

Narration Frameworks

Ready-to-use scripts adapted for developer content. Keep the rhythm, modify specifics.

The Contrarian Reveal 40s
0-5s Hook: "Stop doing [common practice]."
5-15s Problem: "Here's why it fails: [specific reason]"
15-25s Solution: "Instead, do [your approach]"
25-35s Proof: "I [result] in [timeframe] using this"
35-40s CTA: "Follow for more unpopular truths"
The Build Process 40s
0-5s Hook: "Building [feature] for [app]. Here's what I learned"
5-15s Constraint: "The challenge: [technical problem]"
15-28s Solution: Walkthrough (show code/process)
28-35s Result: Screen recording of working feature
35-40s CTA: "Shipped [X] in [time]. What should I build next?"
The Metrics Update 40s
0-5s Hook: "Day [X] building [app] — here's where we are"
5-15s Numbers: downloads, revenue, users on screen
15-25s What changed: "Since last update: [specific wins/failures]"
25-35s Next move: "This week: focusing on [specific thing]"
35-40s CTA: "Subscribe to watch [outcome]"
The Quick Win 20s
0-3s Hook: "I just saved [X] hours with this one [thing]"
3-15s Demonstration: Quick screen recording of the thing
15-20s CTA: "Link in bio if you want the same"

05 / Operations

Production Workflow

From raw footage to published Short. The actual process for consistent output.

01

Capture

Screen recordings, code demos, Hermes outputs. Record in 9:16 vertical. Capture in segments — don't try to record perfect takes.

Tools: OBS, Screen Studio, iPhone screen recordings

02

Edit

Tight cuts. Remove dead air. Jump cuts between key moments. Add captions (80% watch with sound off).

Tools: CapCut, Descript, Screen Studio

03

Caption

Word-by-word captions, not full sentences. Synchronized to audio. High contrast text (white on dark or black on light).

Style: Bold, sans-serif, 48-72pt on mobile

04

Thumbnail

Bright backgrounds. One focal element. Text minimal but readable. Faces help if using them.

Format: 1280x720, but Shorts uses first frame from vertical

05

Schedule

Prime time: 8-11am and 7-11pm in your audience's timezone. Post when you can reply to comments in the first hour.

Frequency: 1-3x daily for growth, 1x daily for maintenance

Automation Tools

Agent Tina / Hermes
Script generation, hook ideation, caption formatting
Notion Database
Content calendar, idea backlog, performance tracking
Screen Studio
Automated zooms, smooth cursor, auto-edits
CapCut API
Batch captioning, template-based editing