Civics, the Constitution, and Elections as a System
I care about civics the way I care about infrastructure: it’s the shared system underneath everything else, and it works best when people understand it and take part in running it. This page is about two things I care about a lot, the Constitution and how elections actually get run.
A document I’m passionate about
In high school I took the We the People class, the Center for Civic Education’s program on the Constitution and its history. It’s supported by Congress, and it ends with a simulated congressional hearing where students defend their reading of the document to a panel. I took part in the hearings on the 14th Amendment, which covers citizenship, due process, and equal protection. I was hooked on the Constitution, and I still am.
What stuck with me wasn’t memorizing clauses. It was learning how differently people think about the same words, and why. Understanding how someone reached their view, not just what the view is, is the most useful thing I took from the class. It’s also a good habit for an engineer.
The other thing that stuck is the idea that the Constitution is a living document. The framers built an amendment process in on purpose (Article V), because they expected the country to change. It has been amended 27 times, and only once since 1971, when the voting age was lowered to 18. The most recent amendment, the 27th, was ratified in 1992, but it was first proposed in 1789. I’m not here to tell you what to amend. But it makes me a little sad that we have mostly stopped using the tool the framers gave us, and I’d like more of us to know it exists. That’s the same instinct I bring to software: a system that can’t be updated safely eventually gets worked around.
If you want something shorter on the same theme, I wrote about why the Gettysburg Address still gets me.
Running a polling place
I serve as an election inspector for the New York City Board of Elections, as a Ballot Scanner Inspector. It’s one of the most hands-on lessons in trust I’ve had. A polling place is a small distributed system, and it’s designed so that nobody has to take anyone’s word for it.
- No single person is in charge of a machine. Scanners are overseen by two inspectors, one from each major party. That’s the two-person rule: every important step has a second set of eyes.
- Tamper evidence is the security model. Each scanner is sealed, and the seals are numbered, color-coded, and checked against a written report. You can’t always prevent someone from touching a machine, but you can make it obvious if they did.
- Chain of custody is a log. At the start of the day we check every seal against the report. At the end we print the results, lock and seal the machine, and both inspectors sign. It’s an audit trail, built on paper and signatures instead of a database.
- There is a fallback for failure. When a ballot jams or something stops working, there’s a defined procedure for handling it, carried out by a bipartisan team, and no one improvises.
- The human interface matters. Part of my job is helping voters feed their ballots into the scanner without ever looking at what they marked. That means explaining what’s happening, calmly, to people who may be nervous. Good UX and good privacy are the same job here.
My duties are to open and close the scanners, make sure they’re working and secured all day, support voters at the scanner, and complete the security reports on every seal. None of it is glamorous. All of it is the kind of boring that makes people trust the result, which is exactly the kind of reliability I like.
Why it connects
Elections, like flights and payments, work because of redundancy, handoffs, audit trails, and a shared belief that the system is being run honestly. Trust isn’t automatic: it’s engineered, and then it’s earned by people doing dull, careful work every day. If you’ve ever thought about volunteering as a poll worker, I’d encourage it. The NYC Board of Elections has details.
You can also read more about the other systems I’m fascinated by, or head back to About.