Markdown, Multitasking, and Momentum

Yeah—now for the next post.

I just vibe coded a new feature that allows Markdown in blog posts, and it only took about an hour to wire up. No big planning session, no grand architecture—just a clear idea, some iteration, and a surprisingly smooth path to “done.”

One of my favorite parts of this little win is how light it felt. While the code was compiling and tests were running, I cleaned the kitchen. By the time the counters were wiped down, the feature was basically finished. There’s something deeply satisfying about shipping software and tidying up physical space at the same time—like progress on multiple layers of reality.

Now that Markdown is supported, writing posts feels frictionless. I can focus on thoughts instead of formatting, structure instead of syntax. Headers, lists, emphasis—it all just works, and it fits perfectly with the rest of this project’s philosophy: simple tools, low ceremony, fast feedback.

This is really cool.

Tiny features like this add up. Each one makes the system feel more alive, more inviting to use. And the easier it is to write, the more likely I am to actually do it—which, ultimately, is the whole point.