This site is where I want project work to land once it is past the rough-sketch phase.
Some posts will be short build logs. Some will be longer postmortems. The common thread is that they should explain what I built, what broke, what changed, and what I would do differently next time.
What this site is for
- shipping notes for side projects
- infrastructure writeups
- practical experiments that are worth documenting
- lessons that would otherwise disappear into terminal scrollback
Why start simple
The blog is intentionally file-based.
Posts live as markdown in the repo, which keeps publishing fast and removes any CMS overhead. If the writing flow becomes a problem later, I can replace the content pipeline without replacing the site itself.
What comes next
The first real posts will probably cover active builds, deployment choices, and the small implementation details that usually never make it into a polished launch thread.