Blog
Setting a number is easy. Keeping it green takes tooling and culture.
A performance budget without enforcement is a wish. Wire LCP, JS payload, and image weight into CI so PRs that blow the budget fail loudly.
Culture matters: celebrate PRs that make the site faster. Speed is a feature. On content sites — static HTML, minimal JS, modern images — gets you 90% of the way.
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.
Why I ship static-first when I can
Static HTML is still undefeated for content sites — here's how I decide when to reach for it.
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.
From side project to something people use
The unsexy work: auth, error states, empty states, docs — the gap between demo and product.
