The reason I created a blog section on my website

You don't learn much about a person by reading their background. Sure, you get to know the major things that they have accomplished or are proud of over the years, but you don't really get to hear their voice, or learn how they think in any substantial way. Fundamentally, a resume is someone selling themself, presenting themself in the best possible light. I want this blog to be a place where I can post not only large accomplishments, but small day-to-day wins. At least, that's what I hope for.

I visit a lot of websites with blog sections, but they are often (1) infrequently updated and (2) lacking content/substance.

I think it would be cool to document what I'm working on, but it seems easy to fall into this aforementioned trap, as many before me have.

If anyone's wondering how I set this up, I wanted to make it as easy as possible to write posts without spending a long time formatting code for each article. I wanted consistent styling and Markdown seemed like the obvious choice. I used gray-matter which parses YAML for title, date, and description, and parses the Markdown content. Then I used next-mdx-remote to render each page as React components at build time.

So a one-line post looks like this:

---
title: "Post"
date: "2026-02-27"
description: "Description"
---

Markdown **content** here.

where the link is determined by the file name.