When municipal APIs go dark, citizens don't see a server error. They see closed intake windows for housing assistance, frozen permit queues, and courts that can't process traffic tickets. We usually look at public sector tech through a lens of technical debt. We scoff at legacy stacks and clunky schemas, assuming a rewrite in Go or Node would fix the whole mess. That diagnosis misses how public code actually gets built, deployed, and abandoned.
Cities procure software through RFPs that reward the lowest bidder over the most sustainable maintainer. A vendor wins a contract, delivers a monolithic app, and moves on. Once the warranty expires, internal IT inherits a black box with zero docs, hardcoded config values, and proprietary dependencies. When a security patch drops or an upstream library deprecates, the city has no budget or engineering bandwidth to handle the migration.
Private enterprise absorbs software failure through lost revenue. Public software failure means people lose access to basic human services. When an unemployment portal crashes during a surge, the friction hits people who can't afford the downtime. We're running critical civic infrastructure on fragile supply chains, and our industry has been slow to care.
Part of the fix requires changing how we treat open source in government. For years, cities dumped municipal code repos onto GitHub to satisfy transparency mandates. Those repos are ghost towns. A repo published without ongoing community or maintainers is just digital landfill. Open-sourcing code isn't the same as building public infrastructure.
Civic tech teams need to focus on modularity and docs instead of feature bloat. Stop building monolithic portals that try to solve every agency need in one interface. Build decoupled services with clean contracts instead. If a housing intake form relies on a flaky legacy database, isolate that integration behind a robust adapter so the failure domain stays small.
There's also a massive talent drain in local government. Engineers with modern systems experience rarely take municipal jobs because the tooling is archaic and the bureaucracy is paralyzing. Until cities empower internal engineering teams to make architectural decisions instead of acting as ticket-takers for outsourced vendors, public software will keep falling behind.
The next time you use a municipal website that feels designed to keep you out, remember that bad UX is a policy choice. Code is policy written in a syntax that runs against our neighbors' lives. Treating it with real engineering rigor is the only way to fix it.
