Why I am Returning to Blogging After 15 Years

Then came the era of social media. Twitter, Facebook, then Instagram, TikTok. Blogging became "uncool." "Who's going to read long texts when you can just tweet?" – I thought.

And for 15 years... I stayed silent. I read, learned, grew as a developer, but didn't share publicly. Now, in 2026, I'm returning to blogging. And I want to tell you why.

What Changed in Tech

The Internet is Drowning in Noise

In 2010, when you searched for a solution to a Rails problem, you'd find 5-10 quality blog articles – detailed, thoughtful, written by people who genuinely understood the topic.

Today? You search the same question and get:

• 500 AI-generated articles that look professional but are shallow
• Stack Overflow answers from 8 years ago that no longer work
• YouTube tutorials where you skip 3 minutes of intro and sponsors to get 30 seconds of actual information
• LinkedIn posts that are more self-promotion than knowledge

There's no depth. There's a lack of people sharing real experience, not just another rehash of documentation.

AI Changed How We Work

ChatGPT, GitHub Copilot, Claude – AI tools have fundamentally changed programming. But paradoxically, this makes human experience more valuable than ever.

AI can generate code. It can explain syntax. It can even debug simple problems.

But AI can't tell you:

• Why a particular architectural decision will bite you in 6 months
• What it feels like to migrate a production database with zero downtime at 2 AM
• The subtle trade-offs between different approaches that you only learn after shipping to millions of users
• How to navigate team dynamics when advocating for technical debt reduction

That's what I want to write about. Not "how to write a for loop in Ruby" – AI does that better than I ever will. But the messy, human, experience-driven insights that come from 15 years in the trenches.

The Industry Matured (And So Did Its Problems)

In 2010, we were figuring out how to build web apps that didn't crash. How to use Git properly. How to deploy without FTP.

In 2026, we've solved those problems. But we've created new ones:

• Scale complexity: Going from 1M to 100M users isn't just "add more servers"
• AI integration: Every product now needs AI, but most teams don't know how to build it responsibly
• Technical debt at scale: Legacy codebases that are 10+ years old and critical to billion-dollar businesses
• Burnout epidemic: The industry moves faster than ever, and people are exhausted

These are the problems I'm living through. And I suspect I'm not alone.

Developer Communities Fragmented

In 2010, you knew where to go: Ruby forums, Rails subreddit, a handful of quality blogs.

Now? Discord servers, Slack communities, Twitter/X threads, LinkedIn posts, TikTok coding tips, podcast snippets. Information is everywhere and nowhere.

I want a place where I can write one coherent piece that explores a topic deeply, not split it into 47 tweets or a 15-minute video that could have been a 3-minute read.

What Changed in Me

From Junior to Senior (and Beyond)

Fifteen years ago, I was learning. Absorbing everything. Trying to prove myself.

Now, I've:

• Built systems serving millions of users
• Led teams through technical migrations
• Made architectural decisions that saved (and cost) companies significant money
• Debugged production issues at 3 AM more times than I can count
• Interviewed hundreds of developers
• Mentored juniors who are now seniors themselves

I have something to say. Not because I know everything – I absolutely don't – but because I've made enough mistakes and had enough successes to have perspective.

I Realized Sharing Accelerates Learning

The irony: The best way I learned over the past 15 years was when I taught others.

When I had to explain how PostgreSQL indexes work to a junior developer, I understood them better myself.

When I wrote internal documentation about our microservices architecture, I found gaps in my own understanding.

When I gave conference talks, I learned more preparing than I did in months of coding.

Teaching forces clarity. And writing is teaching at scale.

I'm Tired of Gatekeeping

There's a culture in tech where you're not "allowed" to share unless you're an expert. Unless you've written a book, spoken at conferences, or worked at FAANG.

Bullshit.

Some of my best learning came from mid-level developers sharing what they just figured out. Because they remembered what it was like to not know, so they explained it clearly.

I'm not DHh. I'm not Linus Torvalds. But I've been programming Rails for 15 years, built real products, solved real problems. That's worth sharing.

I Want to Think More Deeply

Social media rewards hot takes. Quick reactions. Surface-level engagement.

I want the opposite. I want to think slowly and deeply about problems. Writing forces that.

When you're limited to 280 characters, you simplify. When you have 2,000 words, you explore nuance.

I miss nuance.

What I Expect From This Blog

A Record of My Thinking

In 15 years, I want to look back and see how my thinking evolved. What problems I was wrestling with. What solutions worked (and which ones I thought would work but didn't).

This blog is partially for you, but honestly, it's also for future me.

A Way to Connect With Other Developers

I don't want to build an audience. I'm not trying to become a "tech influencer."

But I do want to connect with other developers who are:

• Wrestling with similar problems (scaling Rails apps, managing technical debt, leading teams)
• Interested in deep technical discussions, not just surface-level takes
• Curious about the why behind decisions, not just the how

If even one person reads something I write and thinks "Yes! That's exactly what I'm experiencing!" – that's a win.

An Accountability Mechanism

I learn best when I have to explain what I learned. If I know I'm going to write about it, I pay more attention.

So this blog will force me to learn more deeply. To experiment more deliberately. To document my process.

Honest Reflections, Not Just Wins

Most tech content is either:

• "Look how smart I am! Here's how I solved this impossible problem!"
• "10 tips to 10x your productivity!"

I want to write the messy middle. The false starts. The solutions that seemed brilliant but turned out to be terrible. The times I was completely wrong.

Real experience is messy. I want to capture that.

What I Won't Do

I Won't Follow SEO Best Practices

I'm not optimizing for Google. I'm not keyword stuffing. I'm not writing "Top 10 Rails Gems in 2026!!!!"

I'm writing what I want to write, the way I want to write it. If people find it valuable, great. If not, at least I'm learning.

I Won't Post on a Schedule

"Consistency is key!" every blogging guide says.

Maybe. But I have a full-time job, a life, and limited energy. I'll write when I have something worth saying, not because it's Tuesday and I "need to post."

I Won't Dumb Things Down

I respect my readers' intelligence. If I'm writing about database indexing strategies, I'm going to assume you know what an index is.

There are a million beginner tutorials out there. This isn't one of them.

I Won't Avoid Controversy

If I think a popular framework is overhyped, I'll say it. If I think the industry is heading in the wrong direction on something, I'll argue my case.

I'll be respectful. But I won't be bland.

What You Can Expect

Topics I'll likely write about:

• Rails at scale: Performance, architecture, patterns that work (and don't) at millions of users
• Technical leadership: What I've learned leading teams, making architectural decisions, managing technical debt
• The messy reality of legacy code: War stories from the trenches
• AI and programming: How tools like ChatGPT and Copilot are changing our work (for better and worse)
• Career reflections: 15 years in, what I wish I'd known, what advice is overrated
• Honest post-mortems: Times I screwed up and what I learned

I'll try to write clearly, with examples, and always from actual experience – not theory.

Why Now?

Honestly? Because I finally realized that waiting for the "perfect time" is just procrastination in disguise.

I've been thinking about blogging again for 3 years. "I'll start when I have more time." "I'll start when I'm more senior." "I'll start when I have something important to say."

But here's what I've learned: You don't find time, you make it. You don't wait to be ready, you start and figure it out.

So here I am. Starting. Messy. Imperfect. But finally writing again.

If you're reading this, thanks for being here. Let's see where this goes.