Manifesto
ProvocativemorningWhy developers need to stop doing [common mistake in developer tools]. Lead with conviction.
Built for developers and dev-tool creators — technical decision posts, code reveals, debugging stories, performance work. Copy-paste or auto-fill your AutoTweet queue.
1-click setup
Sign up free. We'll generate 30 tweets in your voice based on this calendar, schedule them at optimal times, and queue them in your AutoTweet dashboard. Edit any, publish all.
We'll never share your email. Unsubscribe with one click.
The X developer audience over-indexes on specific technical detail. Vague tech content ("AI is amazing") gets ignored; specific decision content ('we replaced [tool A] with [tool B] for [specific reason]') earns engagement from other engineers — exactly the audience that becomes customers / collaborators / co-founders.
Times shown as audience-peak slot
Why developers need to stop doing [common mistake in developer tools]. Lead with conviction.
Share a specific number from your developer tool / project this week (e.g., GitHub stars + active users change). Format: "GitHub stars + active users went from X to Y. Here's what changed."
The hardest lesson you learned about low conversion from free to paid this year. Specific situation + what you tried + what worked.
An opinion you hold about developer tools that most developers would disagree with. Defend it with specifics, not vibes.
A 5-minute fix that improved GitHub stars + active users or solved low conversion from free to paid. Specific enough that readers can do it today.
Share a screenshot of a tool, dashboard, or process from your developer tool / project. Caption explains the WHY of the workflow.
What did your developer tool / project feel like this week — energy, focus, friction? One honest sentence.
A 3-step framework you use to solve low conversion from free to paid. Number each step. Explain why each matters.
The exact stack of tools you use to run your developer tool / project. List 5-8 with the specific job each does. Mention prices.
A mistake you made in your developer tool / project that cost time or money. Specific, time-stamped, with the lesson at the end.
An emerging pattern you're seeing in developer tools. Multiple developers doing X — what does it mean?
Anonymized story from a your developer tool / project user — situation, what they tried, outcome. End with the universal lesson.
A direct, controversial-but-defensible take on developer tools. "Most developers are wrong about X. Here's why."
Recap of the week in your developer tool / project. 3-5 specific milestones + 1 honest challenge.
Detailed thread: "How to [fix low conversion from free to paid] in [timeframe]." 5-9 tweets with concrete steps.
Ask developers a question you genuinely want answered about developer tools. Read every reply.
Share one specific metric from your developer tool / project this week with context. "We saw [X] this week. Last week was [Y]. The change was [reason]."
Why you started your developer tool / project. The exact moment / pain / observation that triggered it.
Something you used to believe about developer tools that you now think is wrong. Pivot post.
Recent win in your developer tool / project. Tag the people who helped (only if they're public on X) or thank the audience.
Open-ended question about developer tools that earns substantive replies. Avoid yes/no questions.
Pick a specific example from developer tools and break it down. "Here's why [X] worked. Tweet by tweet:"
A truth about developer tools that nobody wants to say out loud. Lead with the statement; defend it with specifics.
Compare 2-3 tools in your stack that solve similar jobs. Specific tradeoffs, not vague reviews.
Show a specific process from your developer tool / project. Step-by-step. Include screenshots if applicable.
Specific ROI math for a your developer tool / project customer — time saved × hourly rate ÷ subscription cost. Show the math.
A specific encouragement for developers who are stuck on low conversion from free to paid. Acknowledge difficulty, give specific path forward.
Reflective question for developers. Something you wish someone had asked you at their stage.
Major thread: deep-dive on a topic in developer tools. 7-12 tweets. Hook with a contrarian frame.
30-day recap: specific numbers (GitHub stars + active users, milestones), what shipped, what you learned. End with what's next.
Almost never. The technical depth that wins on X (architecture trade-offs, debugging stories, performance work) doesn't reveal competitive moats. Competitors who'd exploit your decisions already know your product anyway. The audience that DOESN'T know you yet learns to trust your engineering.
Technical enough that engineers in your stack nod, not so technical that adjacent engineers can't follow. Specific languages/tools/decisions: yes. Long code blocks: rarely on X (poor format) — link to a gist or blog. Specific numbers (latency, error rates, throughput): always.
Personal projects + open-source: always shareable. Employer work: only with permission, and only at a level of abstraction your employer's PR/security teams would approve. Most engineers underestimate how often employers are fine with specific tech-content shares.
B2B SaaS
30 days of X content for B2B SaaS founders
E-commerce
30 days of X content for e-commerce operators
Coaches
30 days of X content for coaches + consultants
Ghostwriters
30 days of X content for ghostwriters
Marketing agencies
30 days of X content for marketing agencies
Solo creators
30 days of X content for solo creators