About This Blog

I built this blog because I wanted a place to keep track of my own thinking.

Most of what I make never fits neatly into a portfolio page. There are half-finished ideas, experiments that taught me something, notes I want to revisit, and small project updates that matter to me even if they are not “launches.”

This site is where those things go.

What I want this blog to be

I want this to be easy to write in and easy to read later.

That means:

• short notes when I do not have time for a full post
• longer write-ups when something is worth unpacking
• project logs and progress snapshots
• technical notes, personal observations, and everything in between

I care more about usefulness than polish. If a post helps me remember what I was doing, why I made a decision, or what I learned, then it did its job.

Why the terminal look

The terminal-inspired design is not just decoration.

I spend a lot of time working in text-based tools, so this style feels natural to me: focused, quiet, and direct. I wanted the site to feel like a small app window where I can keep notes, not a marketing page.

The design is intentionally simple:

• dark theme
• monospace type
• minimal layout
• small visual details that make it feel alive

It is meant to stay out of the way while still having some personality.

What will be posted here

There is no strict category rule.

Some posts will be technical. Some will be about process. Some may just be short notes I want to keep. The common thread is that they are things I do not want to forget.

If you are reading this later, this post is the starting point.

If you want to see how this site is built under the hood, I wrote a follow-up meta-post about the architecture: “The Software Architecture of This Blog”.