The “Just Be Consistent” Advice Is Lazy. Here’s What Actually Works.

💡 Posting every day for six months and getting nothing isn’t a consistency problem. It’s a quality problem disguised as one. I’m unpacking why consistency advice drives me insane and what I’ve actually found to be more honest and more useful.

I missed last week.

Didn’t post. Didn’t publish. And I’m not going to pretend it was intentional or that I had some grand reason for it. I just didn’t have anything worth saying. And if I’ve learned anything from six months of posting every day and getting almost nothing back — it’s that posting for the sake of posting is its own kind of dishonesty.

So I didn’t. And I don’t regret it.


The consistency advice problem.

Here’s what nobody tells you about “just be consistent”: it’s the laziest advice you can give someone. Not because consistency doesn’t matter, but because it skips over everything that actually makes consistency worth anything.

Most people giving that advice don’t talk about the days where you show up and produce nothing good. They don’t talk about how you’re supposed to sustain quality over time without burning out. They just say keep going. Don’t quit. Post every day. Three tweets and ten comments and you’ll get there.

Like shut up.

I posted almost every day for the first six months. And what I was posting was slop. I’d have a thought, hand it to AI to polish, and publish whatever came back, which was always too corporate, always too clean, never sounded like me. Got connections. Barely got views. Found out pretty quickly that LinkedIn is largely pay-to-play anyway, so without a premium subscription the algorithm isn’t pushing your content anywhere significant, regardless of how often you post.

But the real problem wasn’t the platform. It was that I couldn’t have something genuinely worth saying every single day. Nobody can. And pretending otherwise just produces more noise.


What I actually think quality means.

Not a polished post. Not a viral hook. Something that I could read back and find benefit in. Something that reflects where I actually am, not where I want people to think I am.

The post that performed best for me wasn’t a data analytics insight or a freelancing tip. It was an argument about vibe coders — about how every generation of programmers calls the next one lazy, how we went from assembly to high-level languages and old heads called that lazy too, and how the same thing is happening now with AI-assisted coding. It sparked a real debate. Someone even asked if it was AI-generated, which at the time stung a bit — but looking back, that post had more of me in it than most things I’d written.

The difference? I actually had something to say. I wasn’t filling a slot on a content calendar.


The version of consistency I do believe in.

Not posting every day. Not a rigid schedule. A process.

Something like, two hours a day, showing up, doing the work. You don’t have to define every single task inside that time. You just have to start. Because the hardest part is always the start. Write one sentence. Just one. And more often than not that one sentence becomes two paragraphs because the momentum is already there. It’s like kick-starting a car, all the energy is in the push, not the drive.

Going back to old projects and sitting with them has done more for me than any posting streak. Looking at work from two months ago and seeing clearly what’s wrong with it,  that’s progress. That’s the kind of consistency that actually reshapes how you think.


Why I didn’t post last week.

Because I had nothing of quality to show for it. I could have written something. But it wouldn’t have been real.

The Real Draft exists because I want to document this journey honestly. Not fill a schedule. And an honest week sometimes looks like silence.

That’s not inconsistency. That’s just integrity about what this is for.


Until next time — ponder this:

Are you posting because you have something to say, or because you’re afraid of what it means if you don’t

Leave a Comment

Your email address will not be published. Required fields are marked *