INQUIRING LINE

Why do people in countries newer to AI mostly use it for coding, instead of writing or research?

Why do low-adoption countries use AI primarily for coding tasks?

This explores why, in countries where AI use is still sparse, people mostly use it to write code rather than for the wider mix of writing, analysis and learning seen in wealthier countries. The corpus documents this pattern but only partly explains it.


This explores why AI use in lower-adoption countries narrows to coding instead of spreading across many kinds of work. The pattern is real. Anthropic's Economic Index found that Claude usage tracks GDP per capita: wealthier countries use it for a wide variety of tasks, while poorer ones concentrate on coding Does AI adoption follow wealth and mature over time?. The corpus is better at describing this than explaining it, so what follows combines what the notes say with some reasonable inference.

The most useful idea is that adoption seems to mature in stages. The same Economic Index work found that early usage leans toward handing off complete tasks, and deeper adoption shifts toward collaboration and learning Does AI adoption follow wealth and mature over time?. Coding fits the hand-off stage well. You can describe a function, get code back, and run it to see whether it works. Seen this way, a country focused on coding may not have a different relationship with AI. It may just be earlier on the same path.

A second idea comes from research on where workers actually hand tasks to AI. That delegation clusters in information-heavy work and follows what the technology can reliably do, not where chat assistants happen to be popular Where have workers actually delegated tasks to AI?. Coding is where AI's ability is best established. Developers have adopted it almost everywhere, with 80% using AI tools, even as their trust in its accuracy has fallen Why do developers keep using AI tools they don't trust?. If early adopters anywhere start with the most proven use case, coding is the obvious first stop.

The less obvious point is why broader use takes longer. Benedict Evans argues that making tools easier to build doesn't solve two harder problems. Most people don't see their own tasks as things AI could do, and organizations take time to make the cross-department decisions that wider use requires Does easier tool-building actually solve enterprise adoption problems?. Developers skip the first problem because they already think of their work as something a machine can carry out. So a narrow focus on coding may say less about what AI can do in those countries and more about who has already learned to spot tasks it can take on. Culture may also affect how far people lean on AI: Indian writers accepted more AI suggestions than American writers Is higher AI use by Indian writers a confound to control?. That means adoption differences can't be explained by income alone.

What the corpus doesn't have: no notes test other likely explanations. These include how English-heavy AI tools are, whether software outsourcing work drives the demand, and what subscriptions cost compared with local incomes. Treat the explanation here as a working hypothesis, not a settled answer.


Sources 5 notes

Does AI adoption follow wealth and mature over time?

Anthropic's Economic Index found Claude usage tracks GDP per capita across countries, with wealthier nations showing diverse applications while poorer nations focus on coding. As adoption deepens, usage shifts from delegating complete tasks toward human-AI collaboration and learning.

Where have workers actually delegated tasks to AI?

Workers have committed AI tasks to structured workflows primarily in information-intensive occupations, following technical capability more than conversational LLM adoption. This gradient differs sharply from routine-task automation predictions and wage patterns reverse at advanced degree levels.

Why do developers keep using AI tools they don't trust?

Stack Overflow's 2025 survey shows 80% of developers use AI tools while trust in accuracy fell from 40% to 29%. The primary complaint: AI code that looks correct but contains subtle errors, creating a verification burden that erodes confidence faster than usage grows.

Does easier tool-building actually solve enterprise adoption problems?

Evans argues that reducing coding friction masks two structural barriers: most workers don't see their own tasks as automatable, and enterprise adoption requires organizational decisions that span departments and timelines—not just technical capability.

Is higher AI use by Indian writers a confound to control?

Indian writers accepted more AI suggestions than American writers, reflecting cultural differences in trust and collectivist technology adoption patterns. The authors argue this reliance difference is integral to understanding homogenization, not a confound that obscures it.

Papers this line draws on 8

The research behind the notes this line reads — ranked by how closely each paper relates.