Burke Holland

What I see right now is this sentiment just keeps getting thrown out, but it isn't actually happening.

AI is taking jobs, but not in the sense that it's doing them.

It's taking them in the sense that if you're in tech, that is money that's being diverted to GPUs.

Everybody's investing in GPUs and not headcount.

And if you're in the enterprise, I think a lot of places are using it as an excuse to

to downsize.

It's a convenient scapegoat.

But it isn't taking the job in the sense that, oh, we don't need you because now AI does what you do.

We're not there.

Models are extremely capable.

And so I'm pessimistic that that's actually going to be the case.

And I actually wonder if we don't end up with more developers.

But then you start to ask, well, what is a developer exactly?

And we even have looked at this at Microsoft.

Like, am I an advocate?

Am I a PM?

Am I an engineer?

Or am I all of those things?

Because if there's a feature that's missing in VS Code, I can open an issue, or I could open a PR with three different implementations of that issue done with the AI.

And then we can either approve and say, yes, we're going to do this.