You’re in a country where the government just turned hostile. Your face is in a database. Your location history is logged. Your social connections mapped. The app you spent years perfecting? It’s now the tool that locks you up. This isn’t a dystopian novel. It’s the logical endpoint of a choice you made years ago, when you decided that convenience mattered more than civic hygiene.
Let’s be honest: you’ve told yourself that surveillance is someone else’s problem. That your little startup isn’t building the next Panopticon. But here’s the truth: the same feature that makes your app addictive is the same feature that makes it perfect for a dictator. Ubiquity, efficiency, enforcement — these aren’t neutral design goals. They’re the building blocks of authoritarian infrastructure.
I’m talking about what I call ‘civic hygiene’ — the active decision to avoid building technologies that can be weaponized by a police state. It’s a concept that’s been around since 2013, but almost no one practices it. Why? Because it conflicts with the fundamental driver of the tech industry: growth at all costs.
Take a real example. A game developer built a telemetry system to track player behavior. Simple, useful, harmless. Until someone realized that same system could calculate artillery trajectories. That’s the problem. Everything is dual-use, but software is uniquely scalable, invisible, and modifiable. A hammer can kill, but it doesn’t track every swing. Your app does.
The classic defense: ‘But I’m just building tools. It’s not my fault if someone abuses them.’ That’s the lie. Because the moment you design for ubiquity — the moment you optimize for ‘everyone must use this’ — you’re building a system that can’t be opted out of. And that’s exactly what a police state needs.
Profit doesn’t care about democracy. It only cares about adoption. Capitalism doesn’t need democracy to function. Look at Singapore: authoritarian, efficient, thriving. Investors love that. They don’t ask ‘Could this be used to oppress?’ They ask ‘How many users can we get?’
So what’s the alternative? Civic hygiene means designing for the worst-case scenario. Assume the government will one day be hostile. Build in that assumption. Don’t collect data you don’t need. Make systems that can be turned off by the user. Write code that can be forked, audited, and abandoned. If your app can’t survive a authoritarian takeover, it’s not a feature — it’s a vulnerability.
But here’s the twist: the real enemy isn’t the government. It’s you. Every time you prioritize user growth over ethical constraints, every time you ignore the ‘it could be used for evil’ whisper, you’re making a choice. You’re building the cage, brick by brick, and telling yourself it’s just a scaffold.
The hardest part is that civic hygiene feels like limiting yourself. You’re saying ‘no’ to features that drive engagement. You’re leaving money on the table. But that’s exactly the point. If you’re not willing to lose users to protect freedom, you’re not in the freedom business — you’re in the compliance business.
So here’s the question you need to answer before you write another line of code: Is this feature going to make it easier for someone to round up dissidents? If the answer is ‘maybe’, then you have a decision to make. Build the cage. Or build the key.
FAQ
Q: Isn't all technology dual-use? Why single out software?
A: Because software is uniquely scalable, invisible, and modifiable. A hammer can be used to kill, but it's not designed to track every swing. Software is designed to collect data and enforce rules—that's the difference. The scale and pervasiveness of software make it uniquely suited for authoritarian control.
Q: What should I do as a developer?
A: Practice civic hygiene: design for failure of trust. Assume the government will one day be hostile. Don't collect data you don't need. Make systems that can be turned off by the user. Build in auditable, forkable, abandonable code. If your app can't survive an authoritarian takeover, it's not a feature—it's a vulnerability.
Q: But if we don't build these features, someone else will—and they'll be less ethical.
A: That's the same argument used to justify every arms race. It's a race to the bottom. The real solution is to change the incentive structure, not just build faster. By refusing to build ethically compromised systems, you create market pressure for better alternatives. The 'someone else will' argument is a cop-out that guarantees the worst outcome.