Read the dissent before adopting the explanation

TL;DR: Read an explanation beside a serious dissent. The useful output is a sharper account of what evidence would separate them.

One slide in prawn.shi's essay list does something worth copying: it pairs David Oks's account of Chinese and Indian development with Rohit Shinde's response. Oks places heavy explanatory weight on human development and social transformation before economic liberalisation. Shinde challenges the extent of the claimed social transformation and gives policy a larger role.

The value of reading both is not that two essays settle the economic history. It is that the response exposes which part of a persuasive story needs closer examination. Agreement that education matters does not establish agreement about what explains the difference between two countries.

I would read this pair with three columns: the causal claim, the evidence offered for it and the observation that would weaken it. That last column is the one a reading list rarely supplies. Without it, collecting more references can become a way of protecting an explanation already chosen.

The same discipline is useful in engineering. As an illustration, suppose one explanation for poor tool adoption is inadequate training, while another points to a workflow that adds steps. Both can fit a low usage number.

I would look for evidence that separates them: can experienced users complete the task efficiently, and do trained users return when they encounter the task again? Those observations are more useful than another general argument that either training or usability matters. They could also reveal that both explanations contribute.

I read the two essays' arguments; I have not independently replicated their historical data or adjudicated all their cited research. Their claims about nations remain claims to examine, not descriptions to apply to every individual.

A good counterargument earns its place by changing the evidence you look for next.