Zack Kass

And then I call out something that I think is very important for everyone to acknowledge, which is that asking the question, what jobs are going to automate first actually requires considering what unions are weakest.

Like most jobs are not going to fully automate because most jobs are gonna have exceptional political protection.

And when you make the argument, oh, will the software engineer automate first?

The reason that it's a decent argument is not that cloud code is getting super good.

It is.

But the reason it's a decent argument is because software engineers have no political protection.

They never organize.

They have no union.

And not a single congressperson, except for one or two in Seattle and San Francisco, are going to pass a bill to say we have to protect these people who make $700,000 a year.

And so if you actually play out, wow, why would this group automate?

It's because the politicians aren't coming to save them.

And we see this all the time.

I mean, one of the things I talk about in the book is that the reason that dock workers are not automated right now is political protection.

They went on strike.

They said, you cannot automate the ports.

And we said, okay, you have four years.

We'll keep it the same.

And that brings me to the ultimate point that I will make, and then we'll conclude on this.

People are making job automation an economic issue, and I think it's totally missing the point.

Every time someone says we're going to automate work and that creates economic pain, we talk about the unemployment rate, et cetera.