Most developers do not need more "content ideas." They already have them.
Every week you debug problems, read docs, watch demos, compare tools, test APIs, and explain decisions. That is useful material. The hard part is turning it into public writing without starting from a blank page every day.
The workflow that works best for me is simple:
technical source -> Markdown note -> AI distillation -> X post -> weekly review
Markdown is the key middle layer. It is portable, easy to edit, easy to paste into AI tools, and easy to turn into blog posts, docs, newsletters, or social posts.
1. Start With a Clear Content Promise
Before collecting anything, decide what people should expect from your account.
Examples:
- "I explain AI engineering workflows with runnable examples."
- "I share lessons from building small SaaS tools."
- "I test developer tools and explain the tradeoffs."
- "I turn messy technical docs into practical implementation notes."
The promise matters because it filters your sources. If your account is about AI engineering, not every interesting productivity article belongs in your library.
2. Build a Markdown Source Library
Instead of saving random links, convert useful material into short Markdown notes.
Good sources include:
- docs pages
- technical blog posts
- conference talks
- YouTube transcripts
- podcast show notes
- public X posts or threads
- Reddit discussions
- your own build logs and incident notes
You can use any stack here. A reader app, Obsidian, Notion, a plain folder, or a web-to-Markdown converter all work. For example, I use PDF to Markdown and URL to Markdown for docs and article pages, YouTube to Markdown when a tutorial has captions, and Twitter/X to Markdown when a public post is worth saving as a source note. The important part is not the specific tool; it is getting every useful source into Markdown before asking AI to rewrite it.
Use a template like this:
# Source title
Source:
Topic:
Audience:
## Summary
One paragraph.
## Useful claims
- Claim 1
- Claim 2
- Claim 3
## Examples
- Example
- Code idea
- Workflow detail
## My opinion
What I agree with, disagree with, or want to test.
## Possible posts
- Short post idea
- Thread idea
- Reply angle
This prevents generic AI output. The model has source material, examples, and your opinion.
3. Ask for Angles Before Drafts
Do not start by asking: "Write me a viral post."
Ask for angles first:
Use this Markdown note as source material.
Generate 10 X post angles for developers.
For each angle, include:
- hook
- target reader
- useful takeaway
- format: short post, reply, or thread
Avoid generic motivation. Prioritize practical and technical angles.
One source can become:
- a short opinion
- a checklist
- a mistake story
- a build log
- a tool comparison
- a reply to a common question
- a longer thread
This is where the workflow compounds.
4. Keep a Weekly Queue
A simple weekly queue is enough:
# X queue
## Monday
- Short post from source note A
- Reply to someone discussing topic B
## Tuesday
- Build log from current project
- Tool comparison from source note C
For a developer account, I would rather publish five specific posts than one generic mega-thread.
Good post ingredients:
- a before/after
- a command or snippet
- a tradeoff
- a failure
- a metric
- a strong opinion
- a reusable template
AI can compress the writing, but you should keep the details that make it credible. Before publishing, I like to open the draft in a Markdown Viewer and check whether headings, lists, links, and code blocks still read cleanly.
5. Review What Worked
Every week, save the best and worst posts:
# Weekly review
## Best posts
- Post:
- Why it worked:
- Follow-up idea:
## Weak posts
- Post:
- Why it missed:
- Rewrite:
After a month, you will know what your audience actually wants. Maybe debugging stories beat AI takes. Maybe tool comparisons get followers. Maybe replies build trust faster than posts.
That feedback should decide what you collect next.
Final Thought
Developers do not need to become full-time creators to grow on X.
The better approach is to turn real technical work into a reusable content system:
capture -> convert to Markdown -> distill -> publish -> review
If your posts come from real notes, they become more specific. Specific posts build trust. Trust is what makes technical audiences follow.
Top comments (0)