Chapter 7 · Publish & Repurpose · Lesson 17
Why this lesson: you don't have time to invent three ideas a week for three platforms. You don't have to. One good idea — a bug you fixed — can become a Reel, a LinkedIn post, and a YouTube video. The trick is reshaping the hook for each platform's "Stop," not copy-pasting the same thing everywhere.
Cross-posting the identical file to all three fails because what stops a scroll differs per platform. The idea (the useful thing you know) stays fixed; the wrapper changes. Keep the core lesson, then rewrite only the opening for whatever that platform reads first:
Make the hardest, longest format first and shave down — or make the shortest and build up, whichever fits the idea. For a quick tip, start with the Reel: it forces you to find the sharpest 20 seconds, and that sharpened core becomes your LinkedIn opening and your YouTube pitch almost for free.
One idea → three posts is also three cadence slots filled from a single Create block. This is Lesson 16's batching applied across platforms, not just across days.
The idea: a stale Docker layer cache made your deploy ship old code — you fixed it by busting the cache in the right build step.
Instagram Reel — frame-one text: "Your deploy is shipping OLD code." 25s screen recording of the broken layer → the one-line fix. CTA: "Save this."
LinkedIn post — first two lines: "My deploy 'succeeded' for two days while shipping stale code. The culprit was a Docker layer cache — here's the exact fix." Then the walk-through as text. Repo link in the first comment.
YouTube — title: "The Docker cache bug that ships old code (and the 1-line fix)" + thumbnail: a red "STALE" over a build log. A Short = the reused Reel; long-form = the full debug story.
Same idea, same lesson. Only the opening changed — because each platform's Stop reads something different first.
No clues in the formatting — pick from memory, then click.
Keep the idea fixed; adapt the hook to whatever that feed reads first — frame one, first lines, or title+thumbnail.
LinkedIn shows the first 1–2 lines before "…see more". Native text wins, and any link goes in the first comment to avoid reach throttling.
The Stop differs — frame vs first lines vs title/thumbnail. A wrapper tuned for one feed lands flat on another, even though the idea underneath is the same.