Blog
187 public repos: consistency and good READMEs matter more than any single flashy project.
Recruiters and clients look at GitHub. What they notice first isn't star counts — it's whether the profile looks alive and the repos look intentional.
A good README with problem statement, demo link, and setup instructions beats ten half-finished experiments. Separate original work from forks — both tell a fuller story when labeled clearly.
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.
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.
