Why I Started Writing

To be honest, I didn’t start this because I thought I had some world-changing wisdom to share.

I started because I noticed a loop: I’d learn something cool, feel like a pro for a week, and then realize my understanding was actually pretty thin once I tried to use it again.

Writing is my way of breaking that loop. It’s the ultimate "forcing function."

Thinking out loud

Most ideas feel crystal clear in my head—until I try to type them out.

The second I start writing, the gaps show up. I find the weak spots in my logic and the things I only thought I understood. Reading documentation gives me familiarity, but writing gives me actual clarity.

If I can’t explain it simply in a post, I probably haven't actually learned it yet.

This isn't a tutorial hub

I want to be clear: this isn't meant to be a polished blog or a collection of perfect "How-To" guides.

Think of this more like a public notebook.

Some posts will be deep technical dives, others might just be a random reflection on a Tuesday, and some might even feel unfinished. That’s intentional. This space is about slowing down and thinking deliberately. If a post helps you out, that’s awesome—but the primary goal is just to make sure the things I'm learning actually stick.

The feedback loop

I’m done waiting for ideas to be "perfect" before hitting publish.

Real learning happens in the rough drafts, the mistakes, and the constant revisions. Having this space lets me look back six months from now and see exactly how my perspective has shifted (or hopefully, improved).

Code is great for solving problems. Writing is how I figure out why I’m solving them in the first place.

That’s reason enough to start.

var a = 1

import * as fs from "node:fs";
import * as readline from "node:readline";
 
const fileName = process.argv[2];
const stream = fs.createReadStream(fileName);
const lineStream = readline.createInterface(stream);
 
for await (const line of lineStream) {
  /* parse the content */
}