Jake Cooper

speaker

1,106 appearances 1 recordings 1 series first heard May 2026 last heard 20 May

Jake Cooper’s voice in public audio — every appearance, attributed to the second.

Trend

recordings per month · last 12 months

Recordings per month over the last 12 months — 1 in all, peaking in May 2026 with 1.

Appearances

newest first · ▶ plays the moment

Latent Space: The AI Engineer Podcast · Railway: The Agent-Native Cloud — Jake Cooper · 20 May 2026 podcast

And so we're 100% going to go in and expose those things incrementally.

Yeah, yeah, right?

And I don't want to say we've solved it internally, but it's gotten so good that now we can see those incidents forming pretty quickly.

Yeah, real-time and AI clusters.

Yeah.

So at some point, those will be things that either somebody else goes and builds or we go in and build, but we've always built stuff that was purposeful for us and if it made sense and there was a way to go in and make it useful for users or monetize it or make sure that that loop becomes like a...

profit center instead of a cost center like we want to go in and do that at some point right um so but yeah poor press is definitely dying do you do first party uh feature flagging and uh incremental rollout type stuff as well so we have a feature flagging engine that we built internally that at some point we will we will because i don't see it as a user yeah yeah yeah um so like that that would be that's good right how come you didn't give us what you have well

Because we have to beta test it.

We actually care a lot, a lot, a lot about the quality of the things.

There's plenty of stuff that we've used internally and then we've got it to a point where it doesn't make its way entirely through the journey because it fails.

It's like this holds for one service, but it doesn't hold for multiple services.

So we'd have to go and build these things for multiple services to go and make this work.

And we know for a fact that if we release this thing, we'd have to go and rebuild this thing again

and again and again and some things are worth doing to go in and do that but a lot of them are basically like that also that kind of just informs our roadmap of okay well like for us to go and make that actually a bit easier we can do a few of these things first and then we get to that experience right um we don't want to dilute the experience by basically saying like oh yeah this works but only for this service right um

unless it's like a very, very core initiative, which is like, you know, over the next like few months, we're going to roll out a few things that are like, okay, it works for a single service and then it works for multiple services and then it works multiple services across the environment, right?

But you have to be very, very deliberate about those things.

Otherwise, you end up with a bunch of broken, disparate experiences, which ultimately end up creating a ton of support load because people are like,

How do I use this feature?

How do I go in and do this other stuff, right?

So it's kind of the thing earlier about like you expand your company in general to get those like features and then you almost compact it, smooth out those things.

Showing 901–920 of 1,106 · page 46 of 56