Why I Started Keeping a Dev Blog

Every day at work I run into small insights — a command flag I never knew existed, a debugging technique that saved an hour, an AWS pricing quirk that explained a surprise bill.

Most of these disappear. I forget them within a week.

This blog is an attempt to fix that. Not with long, polished essays (though I’ll write those occasionally), but with a simple habit: write down what I learned today, even if it’s just three sentences.

The two-track approach

TIL — short daily entries. Three to ten lines. No editing, no polish. Just the fact, the context, and maybe a code snippet.

Articles — occasional longer pieces when a topic deserves more space. An AWS cost analysis, how I set up Celery monitoring, that kind of thing.

Why not just use notes?

Private notes work, but they don’t create the slight friction that makes me write more carefully. A blog that’s technically public (even if no one reads it) changes how I write. I explain the why, not just the what.

How to follow along

The TIL page has everything in reverse chronological order, grouped by month. The Articles page has the longer pieces. There’s also an RSS feed if you prefer that.