Chapter 10 · Ship It · Lesson 22

Your publishing plan

Why this lesson: you've learned the whole craft — positioning, pillars, hooks, structure, faceless filming. Now we stop learning and start shipping. This lesson turns everything into a concrete 2-week plan that ends with real posts on your Instagram feed. No new theory. Just a runway to your first Reel.

First, recall From Chapter 2: your positioning is "I help junior & mid-level devs get better at real web/AI/cloud skills by breaking down what I actually build, break and fix" — and your four pillars are Build it · Use it · Ship it · Learn from me. Every Reel in this plan maps to one pillar and serves that one person. That's the filter for what to make first.

Pick the first Reel — a real bug or lesson

Don't brainstorm a "perfect" first post. Look at your actual last two weeks of dev work and grab one moment: a bug that cost you an hour, a config that finally clicked, a command that saved you. That's the Learn from me pillar, and it's the easiest faceless Reel you'll ever make — screen recording plus on-screen text. The bar is not "impressive." The bar is "true, and useful to a junior dev."

Write it down as one line: "The [X] mistake that cost me an hour — and the one-line fix." That line is your hook and your whole plan for Reel #1.

Batch-record, then set your slots

Creating one post at a time is how people quit. Instead, batch: pick three real bug/lesson moments and record all three screen captures in one sitting. Recording is the expensive part — do it in bulk while your setup is open. Editing and captions can happen later, per post.

Then commit to 2–3 post slots a week — fixed days and times you'll publish, decided in advance so "when do I post?" is never a question [Instagram — Creator Best Practices]. A schedule you can keep beats an ambitious one you'll abandon.

Define done — published, not perfect

The single most important line in this course: done means published. Not "done means I'm proud of it." Your first Reels exist to get you reps and real feedback — polish comes from volume, not from staring at take #14. Before you hit share, run the ship checklist: hook in frame one, captions on, one CTA, maps to a pillar. If those four are true, it ships. That's the whole gate.

Worked example · Nitesh's fortnight

Week 1 — Record. Mon: list 3 real bug/lesson moments from recent work. Tue–Wed: batch-record all 3 screen captures in one sitting. Thu–Fri: edit, add captions and one CTA to each. End of week 1: 3 finished Reels sitting in drafts.

Week 2 — Publish + review. Post Reel #1 Mon, #2 Wed, #3 Fri (your three slots). After each, note what the hook was and one thing you'd change. End of week 2: 3 Reels live, and a short list of lessons for the next batch.

Notice: only one week is "making." The plan is deliberately small. Three imperfect Reels published beats a perfect one you never finish.

Quick self-check

No clues in the formatting — pick from memory, then click.

1. What's the best source for your very first Reel?

Your Learn from me pillar. A real bug you fixed is credible, easy to record faceless, and useful to a junior dev — content only you can make.

2. Why batch-record several Reels in one sitting?

Setting up to record is the friction that makes people quit. Capture three moments at once, then edit and publish them across your slots over the following days.

3. In this plan, "done" means…

Done beats perfect. If hook, captions, one CTA and a pillar are all present, it ships. Polish comes from volume, not from a fourteenth take.

Your turn · do this now Write your fortnight on one page: three real bug/lesson moments for week 1, and your three post slots (days + times) for week 2. Use the ship checklist as your grid. Paste it to me and I'll sanity-check whether it's shippable or still too ambitious.
Primary source · study this Colin & Samir are the sharpest voices on the mindset and business of being a creator — consistency, showing up, and playing the long game over chasing one viral hit. Watch one episode with your fortnight in mind: they'll tell you the same thing this lesson does. Ship, then repeat.
💬 Your teacher is here. Not sure which bug to pick, or whether two slots is safer than three? Paste your draft plan — narrowing it to something you'll actually finish is exactly what this lesson is for.
← Lesson 21 Ship checklist Lesson 23 →