operations · career · reliability
What Running Government Systems Taught Me About Software
Five years operating internal government tech changed how I write code — and what I think 'reliable' means.
People imagine government IT as slow and old. After five years operating systems like CMS, FIR, PKM, and eFOAS at Punjab Police, I learned something more useful: reliability is a human property, not just a technical one.
The system is only as calm as its operator
A tool that confuses the person using it will produce bad data no matter how elegant the backend is. I started designing for the tired operator at 2 a.m., not the ideal user in a spec.
Audit trails beat cleverness
When something goes wrong — and it will — the question is never “did it fail?” It’s “what exactly changed, and by whom?” That’s why I built offense-change tracking into the CMS Extension. Accountability is a feature.
What I carry into my own projects
- Quiet interfaces. Less animation, more clarity.
- Reversible actions. Every destructive step should be traceable.
- Graceful degradation. The system should fail small, not fail loud.
Operations taught me that software’s job is to reduce surprise. Everything else is decoration.
Enjoyed this? Say hello →