Hello World: Starting My Developer Blog

After years of reading other engineers' blogs and taking notes in private Notion pages, I finally decided to make the leap and start writing publicly. This is my first post, and I want to share the why behind it.

Why Write at All?

Writing is thinking. Every time I force myself to explain a concept in plain English, I discover gaps in my own understanding. The "rubber duck" effect — but the duck can read.

There are three concrete reasons I'm doing this:

Solidify knowledge — Teaching something is the fastest way to learn it deeply.
Build a trail — Future me will thank past me for documenting the decisions and dead ends.
Give back — Stack Overflow and countless blog posts got me here. It's time to contribute.

What I'll Write About

Expect a mix of:

Deep dives into technologies I'm actively using (Next.js, TypeScript, Go, Postgres)
Architectural decisions and the tradeoffs that come with them
Productivity workflows for engineers
Occasional opinions on the state of the industry

My Current Stack

Here's a quick snapshot of what I reach for on a daily basis:

const stack = {
  frontend: ['Next.js App Router', 'TypeScript', 'Tailwind CSS'],
  backend: ['Node.js', 'Go', 'PostgreSQL', 'Redis'],
  infra: ['Docker', 'GitHub Actions', 'Vercel'],
  tools: ['Neovim', 'Warp', 'Raycast'],
}

The Blog Itself

This blog is intentionally simple: Markdown files committed to the same Git repo as the portfolio. No CMS, no database, no vendor lock-in. A fs.readFileSync and a remark pipeline are all it takes.

"Simple systems have fewer places to break." — every senior engineer after their fourth on-call incident

What's Next

The next posts are already outlined:

My full-stack starter kit — the exact setup I use for every new project
Postgres vs. MongoDB in 2025 — when to reach for a document store
Making React Server Components click — the mental model that finally made it make sense

Thanks for reading. See you in the next one.