Blog
Static HTML is still undefeated for content sites — here's how I decide when to reach for it.
Most personal sites and marketing pages don't need a server. Static generation gives speed, security, and simpler hosting for free.
My default is Astro + typed data. Interactivity only where it earns its keep. When an app needs auth, realtime, or user data — reach for a backend.
Static-first isn't anti-dynamic — it's knowing which tool fits without over-engineering the parts that don't need runtime flexibility.
Infrastructure as a product, not a pile of servers
Why Kilat Cloud is built as an abstraction layer — API-driven provisioning instead of manual config.
Troubleshooting across the full stack
App → OS → storage → network → virtualization → hardware → provider. Real incidents rarely respect layer boundaries.
What managing 40+ Linux servers taught me
Patterns from enterprise/dedicated server operations: monitoring, failover, automation, and out-of-band hardware.
Your GitHub is a portfolio — treat it like one
187 public repos: consistency and good READMEs matter more than any single flashy project.
Accessible by default, not as an audit
Focus states, contrast, and semantics are cheaper to bake in than to retrofit.
Performance budgets that actually stick
Setting a number is easy. Keeping it green takes tooling and culture.
From side project to something people use
The unsexy work: auth, error states, empty states, docs — the gap between demo and product.
