American History to 1877

I took HI 151 as an elective, figuring I needed to balance my engineering focus. Foner's Give Me Liberty! and Boyer's Salem Possessed taught me something unexpected: that rigorous argument and evidence are not unique to computer science. They're just as central to history, and the stakes are higher.

The course spine was American history from colonial times to Reconstruction. But the real lessons came from the historiography—how do historians know what they claim? What evidence is sufficient? When do we speculate?

Evidence-based narrative

Foner builds his narrative on documents, laws, and demographic data. He doesn't just assert "slavery was central to colonial Virginia"—he quotes slave codes, shows census records, traces the evolution of slavery from indentured servitude. The argument emerges from the evidence, not the other way around.

This changed how I think about writing. In computer science, we prove theorems or run experiments. In history, you read letters, count mentions in newspapers, examine archaeological remains. But the rigor is the same: every claim needs support, and you acknowledge where evidence is thin.

Boyer's Salem Possessed was the pivot moment. The book argues that the witch trials in Salem (1692–93) had social origins—that the accusers were from poorer, inland families, while the accused tended to be from wealthier merchant families on the coast. It's a material explanation for a supernatural panic.

He defends this with maps, tax records, and prosopography (detailed study of individuals). The argument is not perfect—some outliers don't fit the pattern—but he acknowledges them and doesn't pretend they don't exist. That intellectual honesty is how you build trust.

Causal reasoning under uncertainty

The final essay asked us to explain the causes of the American Revolution. Foner presents multiple: ideological (Enlightenment thought), economic (restrictive mercantilism), and political (representation). He doesn't claim one cause explains everything. Instead, he traces how these threads entangled.

Writing that essay, I realized: this is exactly what we do in debugging. Multiple factors interact; you can't isolate one. But you can build a narrative that shows how each contributed, and you can be honest about what you don't know.

The Salem case is instructive here too. Social origins theory is compelling, but it's probabilistic. Boyer can't read minds; he can't know that the merchant families were accused because of their wealth. He can show correlation and argue plausibility. That's the best history can do, and it's more honest than confident speculation.

What stuck

I went into the course assuming history was about memorizing dates and names. I left understanding it as a craft of argument. You gather evidence, you construct a narrative that makes sense of it, you acknowledge gaps, and you invite critique. Those are the same principles I use in code review.

Foner and Boyer also taught me that context is everything. A slave code in Virginia in 1660 can't be understood without knowing that slavery was still taking shape, that alternatives existed, that labor systems were being negotiated. That contextual thinking transfers: a bug in one system can't be diagnosed without understanding the whole pipeline.

The course also made me more skeptical of grand narratives. The Revolution wasn't inevitable, and slavery wasn't ordained. They were outcomes of choices, pressures, accidents. That humility about causality is rare in computer science, where we often assume determinism. Historians are more comfortable with contingency.

I'm grateful to have taken this course. It made me a better reader of sources, more careful with claims, and more aware that evidence-based argument is the lingua franca of all serious thinking.