Blog
The unsexy work: auth, error states, empty states, docs — the gap between demo and product.
Between demo and product: auth flows, password resets, 404s, loading skeletons, empty states, rate limits, and error messages that don't blame the user.
Pre-launch checklist: can a new user sign up and recover their account? Does every form handle failure? Is there a way to contact support?
Side projects become products when someone who isn't you can use them without you in the room.
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.
Performance budgets that actually stick
Setting a number is easy. Keeping it green takes tooling and culture.
