And twofold, why would a sponsor want to sponsor a conference when they know a majority of the people are going to be inside watching the talks? And is it relevant for them to even do that still? Yeah.

Well, yeah, you know, it's funny.

I'll say this.

Just like you were saying about the people, I mean, the sponsors loved it, too, that they were there.

And that's a big part of it.

They were talking to everybody.

We had zero problem getting sponsors for Chain React.

How did this come to be? So what's great about

No, it's 100%, right?

That's the key parts, right? So to go with the article, where you're at now.

Certainly.

There are three roles that I've positioned this as.

And one of them, yeah, you can call first off, is like the vibe coder, is basically the person who has some set of skills in understanding what the experience of the app needs to be.

It's like, let's go ahead and steal men vibe coding, right? Let's talk about this.

This person's focused on on quickly iterating features and understanding what the app should feel like, do, and have in a way that sprint-based application development can't even keep up with.

Your built-in meeting is

And they were not speaking.

They were not allowed anywhere near there.

That hurt React Native for at least a year.

But the adoption and the community really worked together.

And it was a U.S. React Native conference.

And then our good friends at Callstack had their conference, I want to say, later that same year.

So they had the Polish React Native conference was React Native EU.

What would you say to people who ask how a like a consultancy like ours who builds apps for a living? How did we even get into throwing a conference? How did that happen?

Yeah.

And that we're, we're all getting these insane capabilities, and when everybody's pushing code, there's this new problem that's cropped up that didn't exist before-That, you know, it doesn't matter so much for us at Infinite Red, 'cause we're all staff level engineers.

Like, we can read all the code, and I don't think a single reputable person here would ever say, "It works, ship it," or say, uh, w- you know, "Hey, why'd you commit that code?" "Oh, that's because that's what Claude told me to do," right? It, it, it's...

There's another level beneath that where we have a care for the craft.

But at the same time, you've got junior developers also ready to ship features and options at a light speed, looking to kind of get these visions of what the app could be.

Somebody who understands the business logic can say, "Instead of talking to people and losing my idea through telephone, I can go through 50 iterations, then say, 'This is what I want.'" And that, that changed overnight, because the gatekeepers are no longer who knows what the code is, and then we're all submitting code at the same time, and that's what you were saying, like, it makes it flat.

Everybody's got master access.

[laughs]