Every guide gives you a number. Post daily. Post three times a week. Post twice a day on X and weekly on LinkedIn.
The numbers are made up. What matters is the relationship between two things that pull against each other.
The two forces
Consistency builds an audience. Gaps kill accounts. Someone finds you, checks the profile, sees nothing for six weeks, and does not follow. Regularity is evidence that the thing is alive.
Volume degrades quality. You do not have five interesting things per week. Committing to five posts per week means three of them are filler, and filler teaches people your posts are skippable.
Your cadence is whatever number lets you stay consistent without reaching for filler. For most people building something real, that is two or three posts a week, not daily.
Cadence by platform
They genuinely differ, because the formats do.
X tolerates higher frequency. Posts are short, the feed moves fast, and a small observation is a complete post. Daily is sustainable here if you have the material, because the bar per post is lower.
LinkedIn does not. Posts are longer, the feed moves slower, and the same audience sees more of what you post. Two or three a week is plenty. Daily LinkedIn posting from a solo builder almost always means padding.
The mistake is applying one cadence to both. They are different formats with different bars.
Let the work set the pace
The cleanest approach is to stop scheduling and let output decide.
You shipped something? Post about it. You made an interesting decision? Post about it. You hit a bug with a real cause? Post about it. Nothing happened this week? Do not post.
This produces natural irregularity that maps to actual work, which is more honest and usually more interesting than a fixed schedule. The risk is that "nothing happened" becomes a habit and the account dies.
The compromise most people land on: a floor rather than a target. One post a week minimum, whatever happens. Beyond that, post when there is something.
Batching is underrated
The main practical obstacle is context switching. Stopping work to write a post is expensive, so it gets skipped, and the account goes quiet.
Batching solves it. Once a week, look at what you did, pick the two or three things worth saying, write them in one sitting. Post them across the following days.
Writing three posts at once takes less than half the time of writing three posts separately, because you are already in the right mode and looking at the same material.
This is most of why Noomachy DevTracker works the way it does. The scan and generation happen overnight. You look at output rather than starting from a blank page, and the expensive part of the loop is already done.
When to post more
There are periods where volume genuinely helps:
A launch. More frequent posting around a release is expected and not filler, because there is genuinely more happening.
A build sprint. If you are shipping daily, posting daily is honest.
Starting out. The first few months favour volume over polish, because you are building the inventory a profile visitor reads.
When to post less
When it has become a chore. Chore posts read as chore posts.
When you are repeating yourself. Three posts about the same feature from slightly different angles is one post spread thin.
When the work is not interesting yet. Some stretches are plumbing. Plumbing is real work and rarely good content. Let it be quiet.
The number
If you want one: two posts a week on LinkedIn, four or five on X, with the honest caveat that this depends entirely on how much you are shipping.
The more useful rule: never post something you would not read.