← Writing

I've never been good at posting, so I'm giving it one more shot

My LinkedIn says "You haven't posted yet." Here's why I stayed quiet for years, what changed, and the few rules I'm using to try again.

·2 min read

Open my LinkedIn activity tab and it says, word for word, “You haven’t posted yet.” There are a few posts pinned from 2024, and then nothing. For three years I moved platforms between clouds, got them through ISO 27001 and GDPR, and cut cloud bills, and almost none of it exists anywhere outside a Git history.

I’m not a naturally loud person online. I’ve started posting more than once and stopped every time. This is attempt number whatever, and this time I’m writing down the rules before I start.

Why I stayed quiet

Mostly, it felt like noise. Every feed is full of hot takes and “10 tools you need”, and I didn’t want to add to that. When I did draft something, it felt too obvious to post. Of course you should right-size your nodes. Of course the pipeline should enforce the rules. Who needs to hear that?

It turns out a lot of people do. Almost everything I know, I learned from someone who thought their fix was too obvious to write up, and wrote it up anyway.

The other reason was simpler: building felt like the real work, and posting felt like a performance. I’d rather ship the migration than describe it.

What changed

Two things. First, I’m building things of my own now. Auton is an agentic development environment where coding agents work side by side, and MunshiPlus is a free app for wholesale businesses in Pakistan. Building them quietly means nobody finds them.

Second, the way we run infrastructure is changing fast. AI agents can now do a real share of DevOps work, and nobody has settled what they should be trusted with. I’m figuring that out on real systems, every week. Writing it down is how I’ll actually remember what worked.

How I used to think

Wait until it's worth a long, polished post.

How I'm trying to think

Share the small thing while it's still fresh. Polish is optional.

The rules I’m giving myself

  1. Write what I did, not what everyone should do

    A note from real work beats an opinion about everyone else’s.
  2. Short is fine

    A few paragraphs and one real example. If it fits in a post on X, it doesn’t need to be an essay.
  3. No schedule promises

    I’m not promising daily anything. I’ll post when there’s something worth reading.
  4. Reply to people

    Posting is half of it. The other half is answering, asking and learning from the replies.

What you’ll see here

Build notes from Auton, lessons from cloud migrations and compliance work, and what I’m learning about letting AI agents run infrastructure without letting them break it. Practical, from real work, and as honest about what failed as what worked.

If you’re also the quiet type who keeps meaning to start, this is your sign too. Write the obvious thing. Someone needs it.

Want the next one?

New posts and shorter notes go out on LinkedIn, X and Threads. Pick the one you already read.

↑↓ move↵ openesc close