Write for the Web, Not the Algorithm

For years, social media was my default place to share ideas.

Whenever I learned something interesting, finished a project, or discovered a useful tool, my first instinct was to post about it. It felt quick and effortless. Open an app, write a few sentences, press publish, and move on.

At first, that seemed like enough.

But over time, I noticed something strange.

The more I posted, the less I could find my own work.

A useful thread disappeared beneath newer posts. A project update became impossible to search for. A small lesson that took hours to learn ended up living for only a few hours in someone else’s feed.

That was the moment I realized I wasn’t building a body of work.

I was feeding an algorithm.

The Difference Between Posting and Writing

Posting is immediate.

Writing is permanent.

They’re both valuable, but they serve completely different purposes.

A post is designed for today’s attention. It competes with thousands of other posts, and tomorrow it’s already old.

Writing is different.

Writing becomes something you can revisit months later, improve over time, and reference whenever you need it again.

I started asking myself a simple question.

If I want to read this again six months from now, where would I look for it?

The answer was never social media.

It was always my own website.

Why I Started Treating My Website as a Digital Garden

I really like the concept of a digital garden.

Unlike a traditional blog where every article feels like a finished product, a digital garden accepts that ideas evolve.

Some posts start as rough notes.

Others become detailed tutorials after months of experimentation.

Some ideas never become “complete,” and that’s perfectly fine.

That’s much closer to how software development actually works.

We don’t build everything perfectly on day one.

We iterate.

Why shouldn’t writing work the same way?

Instead of thinking about publishing as a final step, I started thinking about it as opening a pull request for my own thoughts.

Every article can grow later.

Documentation Has Unexpected Value

One thing I’ve learned as a developer is that documentation is often more valuable than memory.

I’ve forgotten solutions to problems I spent entire evenings solving.

I’ve rediscovered old Git commands by searching my own notes.

I’ve reused snippets from projects I barely remembered building.

Writing creates a second brain.

It turns experience into something searchable.

Instead of asking myself:

“How did I fix this before?”

I can simply search my own website.

That alone makes writing worth the effort.

The Algorithm Rewards Speed

The web rewards depth.

Those are two very different incentives.

Social platforms encourage frequency.

• Post every day.
• Follow trends.
• React quickly.
• Keep people scrolling.

Your own website encourages something else entirely.

• Think carefully.
• Explain completely.
• Improve gradually.
• Build an archive.

Neither approach is wrong.

But only one creates something that keeps becoming more useful over time.

I’d rather publish one article that helps someone a year from now than ten posts that disappear by next week.

Building a Place That Feels Like Mine

Another reason I enjoy having my own website is the freedom.

There’s no character limit.

No recommended format.

No pressure to optimize for engagement.

If I want to write 200 words, I can.

If I want to write 2,000 words, I can.

If I want to mix technical notes with personal reflections, nobody tells me that’s “bad for the algorithm.”

That freedom changes how I write.

I stop thinking about performance.

I start thinking about clarity.

Writing Makes Me a Better Developer

This was the biggest surprise.

Writing doesn’t just document what I already know.

It exposes what I don’t understand.

Whenever I try explaining something—from Astro’s content collections to AI agents—I quickly discover gaps in my own understanding.

If I can’t explain it clearly, I probably haven’t learned it deeply enough.

Writing becomes another way of debugging.

Except instead of debugging code, I’m debugging my thinking.

My Workflow Today

My workflow has become much simpler than before.

1. Capture ideas whenever they appear.
2. Turn useful notes into drafts.
3. Publish before they’re perfect.
4. Revisit older posts when I learn something new.

Not every draft becomes an article.

Not every article becomes popular.

That’s no longer the goal.

The goal is to leave behind a trail of useful knowledge—for myself first, and hopefully for someone else too.

Looking Forward

I don’t think I’ll stop using social media.

It’s still great for conversations, announcements, and discovering interesting people.

But I no longer treat it as my home.

My website is where ideas get to stay.

Projects can grow.

Notes can evolve.

Experiments can become tutorials.

And years from now, I hope this collection of articles won’t just show what I built.

It will show how I learned.

Because at the end of the day, I’m not trying to win against an algorithm.

I’m trying to build something I’d genuinely enjoy reading when I come back years later.