The AI Triforce: Product Experience Architect, Integrity Engineer, & Systems Engineer

So what's really interesting is everybody is tired of the tools that are out there.

There's so many tools left and right.

There's a new one every day, and someone's like, you have to install this, you have to install that.

And I think people are really looking for philosophies and methodologies that really give them an inkling into the future.

Because I think those see further and they're more reusable as you're kind of going into concepts further.

It reminds me... you know, when new frameworks show up, they have new philosophies that come with them.

But I just showed up with no direction.

Right.

And we're we're sort of playing backwards where we're looking at, well, what are the philosophies that are going to make sure that these go forward? Are we all dead? Is this are we going to have no software developers in the future? Is this the end all be all or is there a new set of skills where we're going to have new job positions and new applications and new concepts that are gonna be jobs that explode into the future where you're ready to say, hey, I have this on my resume, I have that.

And I think that, You know, the history, the more it changes, the more it stays the same.

It's not repeating itself, but sure as hell rhymes.

We've got this new set of things, and there will be new jobs and plenty more of them when people get past this AI fear, in my opinion.

Yeah, I just couldn't help but chuckle whenever you said this new technology came out without a new framework.

It really is kind of like a car just pulled up with no instruction manual whatsoever.

The whole

methodology is new.

I sometimes wonder to myself, man, if you could see some of the software that people are building now or workloads they're making with AI, you would see cars with two wheels, three wheels, 15

wheels, one wheel, every

imaginable assembly possible.

And

also, like, I feel like the same goes for, like, how teams work with AI, right? Like, I mean, everyone is kind of trying different things.

I would have to say the pattern that I see the most, Gant, is, like, you just give every individual engineer access to

cloud code, and you say, oh, no, you're AI-enabled now, you know? Right.

A lot of companies are doing that, and the worst thing that happens is you've got your junior designers sitting there sending pull requests left and right that your senior security engineer would cry about, right? Yeah.

How many times are people going to shove their API keys or get stuck into a certain avenue? And I get it, I get it, because this person didn't used to develop before.