Why I Started Publishing Notes

This is the first note. If you can read this, the Markdown pipeline is working.

Why notes?

I've been meaning to write more about the systems I build. Half-finished drafts were piling up in Obsidian, so I figured I'd start putting the useful ones somewhere public. No promises on cadence — but the goal is to share things I've actually debugged or shipped, not commentary on the news cycle.

What to expect

Mostly:

• Notes from production incidents (sanitized)
• Trade-offs I've made when designing async systems
• Whatever I happen to be reading or rewriting that week

Less of:

• Hot takes
• Tutorials that duplicate the docs

Stack note

These notes are just Markdown files in a folder, rendered safely by the public portfolio and terminal views. No CMS, no database, no comments section — git push is the publish button.

# A snippet, because every first note has one
async def foo() -> str:
    return "bar"

If you want to reach out about anything I write here, the contact section on the homepage has the usual links.