Sample: a self-managed post (not on Medium)

Most of what I write ends up on Medium, but I also built this site with a native blog table in D1 — this post is a sample to check how a self-managed (not link-out) post actually renders here, end to end.

Why self-host some posts

Medium is fine for reach, but a native post means:

• Full control over formatting (code blocks, tables, whatever markdown supports)
• No paywall friction for readers
• The content lives in my own database, not a third party's

Example: a partition key that actually helps

A quick example of the kind of snippet I'd want to render cleanly — partitioning a financial time-series table by year and month before writing it out:

df.write.partitionBy("year", "month").mode("overwrite").parquet(output_path)

And the equivalent read-side pruning in SQL:

SELECT trade_date, symbol, close_price
FROM trades
WHERE year = 2026 AND month = 9

Partition pruning only works if the query filters on the partition columns directly — filtering on a derived expression like DATE_TRUNC('month', trade_date) usually defeats it.

What to check

1. Headings, lists, and code blocks render with the right spacing
2. inline code and bold text look right against the theme
3. Links like this one to the projects page work
4. Both light and dark mode look correct

If this all looks good, the native blog path is ready to use for real posts — not just this sample.