Jill Lepore on Bad Readers in Tech
Silicon Valley likes to think it runs on speed, scale, and smart people. But Jill Lepore’s criticism cuts deeper. The real problem may be tech industry bad readers who skim books, flatten history, and then build products and policies on top of shaky assumptions. That matters now because the companies shaping speech, elections, and public attention are still treated like neutral engineering shops, even when their leaders are making political judgments every day.
Look, reading badly is not a harmless flaw. If you misread history, you misread power. If you misread power, you make systems that reward the wrong behavior and punish the wrong people. That is the core of Lepore’s warning, and it lands hard because it explains so much of the present mess. Why do so many platform leaders sound surprised when their tools do exactly what social systems have always done?
What Tech Industry Bad Readers Get Wrong
- They treat history like decoration. It becomes a quote bank, not a source of constraint.
- They confuse reading with scanning. A summary is not the same as a serious argument.
- They frame social problems as technical bugs. That misses incentives, institutions, and power.
- They move too fast to test their assumptions. Speed can hide bad judgment.
Why Tech Industry Bad Readers Matter for Democracy
Lepore’s critique is not about literary taste. It is about what happens when people with outsized influence fail to grasp the civic consequences of their own systems. Recommendation feeds, ad auctions, moderation rules, and data pipelines all shape what people see and believe. Those are governance choices, whether the companies admit it or not.
When leaders misread the past, they often repeat old mistakes with newer tools. That is the uncomfortable part. A platform team can claim neutrality while still making choices that tilt speech, amplify outrage, or weaken public accountability. The machinery may be digital, but the effect is political.
“If you cannot read a text carefully, you will not read a society carefully either.” That is the spirit of Lepore’s warning, and it should make every product leader pause.
Why This Problem Keeps Showing Up
There is a built-in bias in tech culture toward brevity and certainty. Slides beat essays. Hot takes beat slow reading. And once someone gets promoted for pattern recognition, they may start believing they can infer everything from fragments (they usually cannot).
This is where the analogy helps. Building public-facing software without serious reading is like drafting a bridge from a sketch and refusing to check the load table. It might hold for a while. Then reality shows up.
What better reading looks like
- Read the full source. Do not rely on summaries alone.
- Separate evidence from interpretation. Ask what is stated and what is assumed.
- Check the historical match. Have we seen this pattern before?
- Test the policy impact. Who gains, who loses, and who gets excluded?
What Leaders Should Do Instead
Tech leaders do not need to become historians. They do need to stop treating context like optional reading. A strong review process should include people who can challenge first-order assumptions, not just optimize the implementation details.
That means bringing in legal, historical, and civic expertise early, before a product decision hardens into infrastructure. It also means rewarding people who slow the room down when the room is rushing toward a clean story. Solid judgment often looks boring. That is usually a good sign.
Better reading is a management skill. It shapes hiring, product design, policy, and public trust. And if tech companies want to keep claiming they influence democracy for the better, they need leaders who can actually read what history is trying to tell them.
What Happens Next
The industry can keep celebrating speed and confidence, or it can start rewarding close reading and intellectual humility. Those are different cultures. And only one of them has a realistic shot at building systems that do not corrode public life. Which one will the next generation of tech leaders choose?
