Blog
Focus states, contrast, and semantics are cheaper to bake in than to retrofit.
Accessibility audits late in a project always cost more than doing it right first time: semantic HTML, visible focus rings, contrast ≥ 4.5:1, keyboard paths, honest alt text.
Dark mode that respects prefers-reduced-motion, form errors for screen readers, logical headings — habits that prevent common failures.
Most of this makes the site better for everyone. Clear focus and readable contrast are just good UI.
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.
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.
