Martin Beraja Profile picture
Apr 4 15 tweets 8 min read Twitter logo Read on Twitter
🤖🛑 Hitting the breaks on AI?

(1) Alignment worries: perhaps legit. But don't have much to say.
(2) Job automation concerns: LLMs ≠ robots. Economic arguments for slowing down automation are much weaker for LLMs.

Why? Let's dive in! #EconTwitter #FutureOfWork #AI #ChatGPT
Economists have put forth two main arguments for slowing down technologies that automate jobs and displace workers. The first is based on redistributive considerations. The second is based on efficiency considerations.
In a nutshell, the redistributive rationale is as follows. If automation displaces workers who are relatively poor, then this increases inequality. Absent other tools to directly redistribute (e.g., transfers to workers) a government should curb automation to reduce inequality.
This argument is well developed in work by @jptguerreiro-@SergioRebelo6-Teles; Costinot-@IvanWerning; @akorinek-@JosephEStiglitz.
The redistributive argument is much weaker for LLMs than it was for robots.

Robots automate jobs intensive in routine tasks. These tend to be low-to-middle-wage jobs (think workers in a car manufacturing plant). So automation increases inequality.
From what we know so far, LLMs are likely to automate cognitive-intensive jobs. These tend to be middle-to high-wage jobs (think lawyers or software devs). So LLM-led automation would likely decrease inequality. The redistributive rationale for slowing down automation is gone.
The efficiency rationale is in my paper with @Nathan_Zorzi. See this thread for the argument:

In a nutshell, firms automate excessively because
there is a conflict between how firms and displaced workers value the gains from automation.
The efficiency rationale for slowing down automation relies on two assumptions. First, automated workers are financially vulnerable. They are unable to borrow or don't have enough savings to finance consumption while relocating to a new job. Second, worker reallocation is slow.
Both assumptions seem much less relevant for workers displaced by LLMs than by robots.

Again, LLMs will displace relatively richer workers in cognitive-intensive jobs. These workers are likely to have sufficient savings or able to borrow while relocating to a new job.
That is, in practice, lawyers and software devs are not the first that come to mind when thinking about "financially vulnerable workers." Workers displaced by a robot in a car manufacturing plant in Detroit, on the other hand, much more so.
Moreover, and this is more speculative, relocation is likely to be faster/easier for high-cognitive-skill workers than for high-manual-skill workers.
So, while relevant for robots, neither of the two assumptions that the efficiency rationale relies on seem that relevant for LLMs. The case for slowing down LLM-led automation due to inefficiencies is weak.
In all, neither redistributive nor efficiency arguments seem to support slowing down LLMs due to its impact on workers in a way that do support slowing down robot adoption
AI misalignment remains a valid concern, in principle.

But I’d like to see more formal economic arguments rather than armchair theorizing; to spell out assumptions and evaluate them. At this point, I don’t feel we have such arguments to so confidently call for an AI moratorium.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Martin Beraja

Martin Beraja Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @MartinBeraja

Nov 18, 2022
Taxi to JFK. Driver asks: where are you from? Argentina, I say. Driver turns around. Opens his jacket. He is wearing an Argentinean football jersey with the number 10 in it. I’m from Bangladesh, he says. We are big fans! You don’t believe me? Let me show you. Hilarity ensues…
First he shows me pictures of his house. Big Argentina flag is hanging from his balcony. Then pulls up Youtube. Shows me this video of hundreds of Bangladeshi on the street with the 🇦🇷 jersey.

He calls his brother next (i think). Who do you support in the World Cup? Some short back and forth in Bengali happens (had to look this up, I must confess. Didn’t know the language’s name). The brother starts chanting “Argentina! Argentina!”
Read 6 tweets
Nov 3, 2022
The more credible approaches (in my view) match conditional moments, like responses to a particular shock, not unconditional ones, like this blog.

There is a nice exercise illustrating why in my paper on regional business cycles: economics.mit.edu/sites/default/…

1/n
Think about trying to identify one parameter: how "sticky" wages are. This is a key parameter in many DSGE models. All other parameters are known.

Imagine you have a strong prior that wages are very sticky when the "truth" is that they are rather flexible.

2/n
Suppose we simulate data from a model with the "true" wage stickiness. We then try to estimate the model on this data, given our prior. How much does the posterior on wage stickiness move? That is, when do we get close to recovering the "true" wage stickiness parameter?

3/n
Read 9 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(