Post ideas that survive the day you run out of ideas

Why a small set of formats outperforms inspiration

A blank composer asks an impossible question: what should I say today, about anything, to everyone. A format narrows it to something answerable, such as what broke this week and what fixed it. Narrow questions have answers even on days when you feel you have nothing.

Formats also compound. Readers begin recognising a recurring shape, which makes you easier to remember and easier to describe to somebody else. That recognisability is worth considerably more than the variety you give up.

Formats worth keeping in rotation

These work across most subjects because they draw on things you accumulate simply by doing your job. Choose four or five that suit your material rather than attempting all of them.

• The thing that broke: a specific failure, the symptom, and what actually fixed it.
• Before and after: a screenshot pair with one sentence on what changed between them.
• Received wisdom, examined: a common claim in your field and where it stops holding.
• The small number: one measurement from your own work and what it revealed.
• Question you keep being asked: the answer you already give in private, written once in public.
• Teardown: something you admire or dislike, and the specific decisions that make it so.
• Working notes: a decision you are weighing right now, with the trade-off stated honestly.
• The short list: three tools, papers or accounts you actually use, and why each one earns its place.
• The correction: something you argued previously and no longer believe.

Capture material as it happens

Nearly everything worth posting occurs while you are doing the work, not while you are trying to write about it. A bug that took an afternoon, a question a customer asked twice, a number that surprised you in a dashboard: all of it is gone by evening unless you write it down within a minute.

One note file is enough. Do not organise it, do not draft in it, just capture the raw fact and move on. The friction of a tidy system is exactly what kills the habit, and a messy list of forty half-thoughts is a far better problem than an empty composer.

Mine the work you have already published

Documentation, changelogs, support answers, internal write-ups and old articles are full of posts nobody has seen. A single article usually contains three or four separate ideas that each stand alone, and the readers who saw the original are a tiny fraction of the people who might see the post.

An RSS workflow can help republish work from a feed you own. Twifly automatically schedules matching entries using your format template, keyword filters and publishing schedule. Check the feed preview and settings before launch, then monitor the upcoming posts.

• Break one long article into its separate arguments and publish them weeks apart.
• Turn support answers into posts; a question asked twice will be asked again.
• Revisit strong posts from a year ago with what you have learned since.

Batch the writing, then let a queue release it

Writing five posts in one sitting is meaningfully easier than writing one post on five mornings, because the expensive part is getting into the right frame of mind, and batching pays that cost once. An hour on Monday can cover the working week.

Then let a schedule handle release. Publishing five posts the moment you finish them wastes four of them; feeding them into recurring slots spreads them across the days and hours you already decided were worth using.