Azeem Azhar

And so that backlog moves to knowing what's possible, what you need, what to get right.

It's no longer just an engineering mindset.

It is really a creative mindset.

It's an artist mindset.

Now, a lot of this is classic Jevons paradox.

So, you know, we're bringing down the cost of something, so we're going to do lots of it.

And what's happening is that we're building things that otherwise we simply wouldn't do.

No one was going to build that DJ music workflow for me.

And I'd seen all the tools and I wasted more time searching the web for tools that could do it than it took me to build.

And I certainly wasn't going to pay $10,000 to $15,000 to a dev shop to build it for me.

I was just never going to get it built.

And now it is built, it is being used, and it is in existence.

And this is happening.

You can see that this is rippling through the engineering community if you go onto X. But you also look at Stack Overflow, which had been the place where a lot of engineering knowledge was stored, and Stack Overflow has really collapsed.

People are not asking questions anymore because the AIs are really developing what they need to develop.

I think for software companies, this could be quite challenging because right now I can build a tool faster than it takes to

communicate the the spec so why would i start to accept the shortcomings of someone else's design unless they have some kind of deep lock-in which might be that they are the so-called system of record within my within my enterprise and of course there are all sorts of things we have to consider like are these systems going to be reliable are they going to be safe

How are they going to interact with each other?

Are we going to be able to maintain, keep our data or will they fail and the data has gone for good?

I mean, these feel like they are problems that will get solved over the next year or two.