Lesson 5: Content Ideas and the 30-Day Playbook
you've got the system. you've got the skills. now you need to know what the hell to write about — and a plan for actually doing it. this lesson is the executable. everything before this was the setup. this is where you run the code.
The most common question: "but what do i write about?" The real answer: you already know things. you're just too close to your own knowledge to see what's interesting about it. the solution isn't creativity — it's a query engine against your own experience.
Why Engineers Struggle with Content Ideas
it's not that you have nothing to say. it's that you think you need something new to say. you don't. you need to say something useful to someone who's 2 years behind you.
The 2-year rule: if you have 2 years of experience in anything — software, parenting, cooking, running, anything — you have 2 years of knowledge that someone else doesn't have. you don't need to be an expert. you need to be one step ahead and willing to write down what you know.
the trap: you compare yourself to the top people in your field and think "i have nothing to add." but the people reading you aren't comparing you to the top people. they're comparing your knowledge to their own. if you know something they don't, you're valuable.
The Content Idea Query Engine
run these queries against your own experience. each one generates 5-10 post ideas. this is the only system you'll ever need for never running out of things to write about:
query 1: mistakes
"what's a mistake i made that i now see everywhere?"
every mistake you made as an engineer, a learner, a builder — someone else is making right now. your job is to write the post you wish you had read before making it.
examples:
- "i spent 3 months building a feature nobody asked for. here's how i knew (and ignored the signs)"
- "the worst debugging story of my career — and the 1 thing i do differently now"
- "i used to think code reviews were about catching bugs. i was wrong."
query 2: wizard-level knowledge
"what do i do in my work that would seem wizard-level to me from 3 years ago?"
three years ago, you didn't know something you now do automatically. that thing is content. explain it to your past self.
examples:
- "how i actually read a 10,000-line codebase without drowning"
- "the git workflow i use now that would have saved me 100 hours as a junior"
- "what 'good logging' actually means — explained for someone who still uses print statements"
query 3: changed beliefs
"what's a belief about [my industry] that i used to hold, but now i think is wrong?"
changed beliefs are inherently interesting because they imply a story — you used to think X, something happened, now you think Y. the reader gets to learn from your arc without living through it.
examples:
- "i used to think TDD was a waste of time. here's what changed my mind."
- "i thought microservices were always the answer. then i inherited a monolith that was better."
- "clean code made me a worse programmer. here's what i mean."
query 4: systems and automations
"what's something i automated or systematized that saves me hours?"
if you built a tool, script, workflow, or mental model that makes you faster or better, someone else is doing it manually right now.
examples:
- "the shell alias i use 40 times a day"
- "how i automated my team's deployment checklist"
- "a single bash script that replaced 3 manual processes"
query 5: the FAQ
"what question do people always ask me when they find out what i do?"
if one person asked, a thousand people are googling it. if multiple people ask you the same thing, it's a content goldmine.
query 6: underused tools
"what's a tool or workflow i use that nobody else seems to know about?"
every engineer has a weird, niche tool they love and nobody else uses. that's a post.
query 7: unpopular opinions
"what's something most people in my field believe that i think is wrong or overrated?"
these posts pop off because they trigger conversation. but be specific. "agile is bad" is noise. "daily standups should be async unless you have a real blocker — here's what my team did instead" is a post.
Don't write all of these at once. pick one query. answer it. publish. next week, pick another query. the goal isn't to build a content calendar for the year — it's to build the muscle of extracting ideas from your own experience and shipping them.
The First 30 Days: Your Playbook
here is the actual plan. do not skip steps. do not "optimize" it before you've run it. the first 30 days are about building the habit, not optimizing the output.
days 1-7: the reply game
goal: build the reply muscle. get your name in front of eyeballs. start feeling what it's like to write publicly without the pressure of "creating content."
- Reply to 10-15 posts per day from accounts in your space.
- No compliments. Every reply adds value, asks a question, or shares related experience.
- Each reply takes 2-4 minutes max. Don't agonize.
- Do NOT post your own content yet. Just reply.
- Track which types of replies get engagement (likes, author replies, profile visits).
Total time commitment: ~30-45 min/day.
why only replies for a week? because writing replies is lower stakes, builds the same writing muscle, and already starts the visibility flywheel. it also teaches you what resonates in your niche before you invest in original posts. many people skip this and write 10 original posts into the void that nobody sees because they have no followers and don't understand the conversation culture yet.
days 8-14: start posting
goal: publish one post per day. build the publishing habit. gather data on what works.
- Post once daily. Use one of the format templates from Lesson 3.
- Don't overthink. Write quickly, edit once, publish.
- Continue the reply game (10-15 replies/day).
- At the end of each day, note which post performed and which didn't. Don't judge — just collect data.
- If a post flops, literally nobody cares. If it pops, you have a signal.
Total time commitment: ~60-75 min/day.
The flop paradox: your early posts will flop. that's not a failure — that's calibration. each flop is data about what your audience doesn't care about. the faster you collect flops, the faster you find what works. treat flops as failed tests, not personal failures.
days 15-21: double down
goal: expand your best-performing content. start cross-platform distribution.
- Identify your best-performing post from days 8-14. Expand it into a thread or a longer piece. Publish it.
- Take that expanded piece and cross-post a modified version to one other platform.
- Continue daily posting (1 post/day).
- Continue reply game (you're past 300 replies by now — patterns should be emerging).
- Review your reply data: which types of replies got the most engagement? Which accounts' audiences resonate with your style? Double down on those.
Total time commitment: ~60-90 min/day.
days 22-30: build the owned channel
goal: set up your platform-independent home. start converting public attention into owned audience.
- Set up your newsletter, personal site, or whatever "owned" channel you chose. Write your first issue/post. Publish it.
- Add one clear path from your primary platform to your owned channel. Link in bio. Pinned post update.
- Review your first 3 weeks of posts. What themes emerged? What format works best for you? This is your content identity forming.
- Continue daily posting and reply game.
- At day 30, review: how many posts published? how many replies? which 3 posts performed best? what patterns do they share?
Total time commitment: ~60-90 min/day.
What Happens After Day 30
by day 30, you've built the core habit. you've published ~20+ original posts and ~300+ replies. you have data. you have momentum. you have a system.
your job now is to sustain the system:
- 2-3 original posts per week (quality, using what you learned about what works)
- daily reply game (this never stops — it's maintenance, not setup)
- weekly repurposing (best post → one other platform)
- biweekly/monthly long-form piece (newsletter, blog, video)
- monthly review (what worked? what didn't? adjust your formats accordingly)
that's it. the system is the strategy. most people's marketing "strategy" is "post sometimes and hope." you now have a deployable system. the rest is volume and time.
The Only Thing Left
You have everything you need. you understand the algorithm as a feedback loop. you know how conversations become leads. you can write in a way people actually read. you have a distribution pipeline. and you have a query engine that generates ideas indefinitely plus a 30-day plan to execute.
the gap between where you are and where you want to be is not a knowledge gap. it's an execution gap.
close this lesson. open your primary platform. reply to 10 posts. then write one post. publish it. done.
everything else is just reading about push-ups.
Check Your Understanding
Practice: Run the Engine
Take the 7 queries from this lesson. Run them against your experience. Write down every idea, no matter how half-formed. Aim for 10 minimum. Pick the top 3 that you're most excited to write. These are your first 3 posts.
The 30-day playbook starts now. Not tomorrow. Not next week. Today.
Your only task for today: reply to 10 posts from accounts in your space. No compliments. Add value.
Come back tomorrow and do it again.
This is where most people stop. they read everything, nod along, and never actually start. they bookmark the course. they "come back to it later." later never comes.
if you got this far and do nothing — you wasted your time and mine. if you got this far and reply to 10 posts today — you've already done more than 95% of people who consume marketing advice online.
close the course. open the platform. reply.
1. 1. The 2-year rule says you can create valuable content if:
2. 2. Why should you spend days 1-7 only replying and not posting your own content?
3. 3. What's the best response to a post that flops?
4. 4. The 'changed beliefs' query generates content by asking:
5. 5. After the 30-day playbook, what's the sustainable long-term system?