It's that time of the year where new PhD students have to figure out how to do research. Luckily, the profession has put together a lot of resources to help us all become better researchers, and you can find my collected list of resources here: https://t.co/WJWRRGy7nK
AI is greatly increasing "equality of opportunity" between econ faculty at top schools vs lower ranked schools.
There's a few reasons for this:
Reason 1: At top schools, faculty have funding for grad student RAs, and these grad student RAs are more likely to make substantive contributions to research. At lower ranked schools, both RA funding and RAs' abilities to make research contributions are less likely.
Now, everyone has the same agentic coding tools and is starting from similar blank slates in terms of knowing how to make best use of them. However - for many of the tasks that RAs used to do - agentic coding tools are far more effective, even with very little knowledge of the tools.
So, for many applied researchers, if you can afford $100/mo (more on that later) for a Codex or Claude Code subscription, with little agentic coding skill you will have a productivity advantage over the economist with many resources not making use of these tools.
Reason 2: You may argue that the economist at the top school can purchase more CC/Codex subscriptions, or get them for all their RAs, and this will nevertheless give them a big edge over economists with fewer resources.
However, this ignores a significant bottleneck in the use of AI for economics research: how to verify LLM output.
In many domains of software engineering, it's possible to functionally verify an LLMs output. This means you can parallelize software development with agents by having other agents themselves verify its output.
This type of verification is possible only for some economics research tasks, and developing verification mechanisms usually requires skill in agentic coding and software design.
So, we can assume economists - poorly skilled at agentic coding and software design - are doing all their verification themselves.
Then, if you have several RAs left to their own devices and producing copious LLM output, it's still incumbent on you as the high-resource economist to verify all their output.
Ostensibly this could still save you time relative to producing and verifying yourself, but in practice, for two reasons, there are often quickly *negative* returns to more RAs.
Reason 2A: Switching costs. It's a lot easier to verify when you are the prompter. This is both because you're mentally in flow in your particular research task and with the coding agent, and because you understand - through your own prompting - the process by which you arrived at some output.
Reason 2B: Wasted time verifying useless AI output. Last weekend, I spoke to one economist who described this failure pattern. He delegated a task to his RA, who then produced after some time output for him to review.
However, the standard errors felt very fishy, and it was difficult to sort through the output to a root cause. The economist, believing the RA had mindlessly use Claude Code, asked the RA to come back with a written explanation in his own words of what he did.
A few days later, he got the explanation, which itself seemed to clearly be written mindlessly with Claude. In the end, the economist gave up and did the task himself.
Of course, you could argue that this is the result of poor RA selection or training. But verification is even problematic with well-intentioned RAs' output, because in many situations, if a substantive mistake is made at one point in a chain of tasks, it can make the successive tasks' output not useful.
Reason 3. One dimension of inequality between top schools and lower ranked schools is access to the cutting edge of research, and access to resources helping you understand the cutting edge of research.
Pre-LLMs, as an economist or PhD student at a top school, you'd get more access to researchers at top schools, funding to attend educational workshops, etc.
Of course this remains an advantage of being at a top school, but LLMs make this much less of an advantage than in the past. The reason for this is that current-gen LLMs are 95th percentile quality teachers on any topic in their training sample.
For me, this has been extremely empowering. I was never was very good at micro theory, but recently I've become much more interested in learning select topics in micro theory.
Pre-AI, I would have probably never acted on this interest. It's hard to figure out what basics I don't understand when trying to work through some paper I'm interested in. I don't want to waste my friends' time who can answer my basic questions, and it's a bit embarrassing if there's something really fundamental which I've forgotten or never learned.
Now, for any given topic in its training data (i.e. basically everything), I can use AI to create a step by step curriculum, give me homework assignments, and evaluate my homework assignments (sign up to my newsletter to learn more about how I do this: https://t.co/2SBegUvyKo ).
Sure, there are nuances that AI sometimes gets wrong. But for a motivated student, especially when considering availability of the teacher, AI is a better teacher on almost every topic than almost every economist (see, for example "Law Professors Prefer AI Over Peer Answers": https://t.co/3uNzFnecPh)
The price of AI: One way in which you might argue these tools increase inequality is through cost. At a top school, researchers can afford $400+/month to have both Claude Code and Codex, whereas $100/mo might be all someone at lower ranked schools can afford.
A few points here:
- Very few economists are making full productive use of the $400/mo of subsidized compute from a Claude Code and Codex subscription. They'd see little to no fall off dropping one subscription.
- Almost everyone can afford $100/mo. If you think you can't pay $100/mo, this is actually a question of your willingness to humble yourself. You can tutor undergrads (maybe at a university across town), drive Uber, sign up to do part time data labelling at one of the firms looking for PhD economists, or just sell some shit you don't need.
Yeah it sucks, and if you were at a top school you wouldn't need to consider this, but your only option almost certainly isn't to pay $0-20/month for an AI subscription.
Addendum: I do trainings on agentic coding for economists and create software products/internal tools for policy organizations. If this interests you - check out this page - https://t.co/gG48Y9WQhy - or just DM me. I also have a lot of free educational materials here: https://t.co/Y89oQDgScg
@p_ganong You can link Overleaf to GitHub and then push changes manually. Maybe this is what you didn’t want, but I find that it works very well, even with coauthors. See this guide: https://t.co/k5CMEDCHGI
In #Denmark, higher-income buyers earn higher capital gains on #housing. These different arise due to differences in what low-income buyers can afford, instead of factors like risk aversion or investment skill.
Read: https://t.co/F3gKJFfvif
Subscribe: https://t.co/ZfdVQ6Q6CH
@EkonomiskDebatt nr 4 finns nu online för gratis läsning! Bl.a. om effekterna av utländska företagsuppköp och om konsekvenserna av de nya amorteringsreglerna. https://t.co/sN1kn6qyMy
I posted a brief guide about syncing Overleaf with VS Code, through either Dropbox or Github. This way, you can get the benefit of Claude Code and Codex with the nice collaborative tools offered by Overleaf.
Overleaf guide is here: https://t.co/k5CMEDCHGI
If you haven't used Github, it's actually not that scary and it is made much easier by using a tool like Github Desktop. Of course, Claude can also write commit message and use git for you. It's a new world out there.
Which is your main: Codex or Claude Code for academic research?
@ClaesBackman shares a practical guide, link in replies.
I have to say, getting enough usage limits and quick responses to things that are broken are two factors that made a huge difference for me. I'm using both.
I'm starting a newsletter specifically on AI/agentic coding for economists.
Unlike other excellent newsletters by economists on AI, mine will be primarily focused on what is practically useful for economists.
> model/tool updates which are worth knowing for economists
> new research workflows I'm experimenting with
> lessons I learn from teaching agentic coding to economists (I've taught over 100 economists across individual and group sessions)
> commentary on discussions important to the profession
The first edition will be out Tuesday the 19th. I'll discuss the new /goal feature which has been released in both Codex and Claude Code.
You can subscribe here! : https://t.co/2SBegUv0UQ
I was honored to teach a one-day class at @EDHEC_BSchool on using AI in biz/econ research last week — from chatbots to automated research pipelines.
6 demos featuring work from @cblatts, @ben_golub, @pedrohcgs, @alejandroll10 and others.
Slides + demos: https://t.co/0RAw1vmnr0
Do you run Qualtrics surveys? Then use my GitHub repo to automate the whole process with Codex! Tell Codex what you want to study, and it will create the survey, push to the survey to Qualtrics and generate synthetic responses, download and clean the data, and produce a set of slides summarizing the process.🧵with complete guided example!
@MichelaTincani I mostly use Claude Code, but the Codex app is also very good! I like to be able to see the files at the same time, so that moved me towards Claude code in VS code
And if you prefer to use Codex instead of Claude Code, here is translated version of the practical guide guide: https://t.co/OEg3CFEEeM
I also had Claude and Codex work together to write a comparison between the two: https://t.co/lkaPpLaPXD
I put together a short practical guide for economists who want to use Claude Code, but who haven't gotten around to trying yet.
The goal is to reduce the start-up costs by using Claude Code within VS Code.
Amazing idea by @aniketapanjwani to turn this into a readable transcript. AI is changing the way that we communicate by reducing the cost for e.g. making websites.
Stanford recently livestreamed a 3.5 hour conference with leading economists (@Susan_Athey , Matt Gentzkow, and @ahall_research , among others) on "Empirical Work in the Age of AI"
I turned the whole thing into a readable transcript, separated by talk.
You can pass the whole thing to your coding agent to extract exactly what is useful for you.
Check it out here!: https://t.co/jKtU6mgG1X
I put together a short practical guide for economists who want to use Claude Code, but who haven't gotten around to trying yet.
The goal is to reduce the start-up costs by using Claude Code within VS Code.
@arindube Fully agreed. I worry that focusing too much on producing whole papers with AI will make people miss the real, productivity-improving use of AI. Using AI to eg format CVs for grants is really valuable.
Brief plug for a piece on the boring case for AI: https://t.co/QBBI8CC2zQ