Gergely Orosz

You felt a little bad about it.

You'd remember it the next time, and that feeling kept your judgment sharp.

With AI agents, that feeling is gone.

Now someone else is dealing with the consequences.

The landmines are still there, they just won't blow up on you today, and we don't even pay attention to a lot of these landmines being placed by AI agents.

Finally, I really appreciated Dax's memo to his team.

He basically admitted, we're shipping features we shouldn't, we're absorbing too many hacks, and the worst part is, we're not even moving faster.

We just feel like we are.

That's a pretty brave thing for a founder of a hot AI native startup to say out loud.

And I think it's a reality check that a lot of engineering teams need right now.

If you enjoyed the episode, be sure to subscribe on your favorite podcast platform or on YouTube.

And if you'd like to support the show, leaving a rating or review really helps.

Thanks for listening and see you in the next episode.

Rust is quietly spreading as a language of choice to build reliable and performant applications.

But what makes it different?

Alice Riel is a software engineer working on Google's Android Rust team, a core maintainer of Tokio, the de facto async runtime for Rust, and is a Rust language team advisor.

In today's conversation, we cover the pitch on why Rust is worth to consider whether you are using TypeScript or C++ today.

how concepts like ownership, the borrow checker, and the unsafe keyword work, and what are things that trip up newcomers to Rust, how the languages govern without a benevolent dictator, and how RFCs and additions work, and many more.

If you want to understand what makes Rust different and why so many engineers say, once it compiles, it works, this episode is for you.

This episode is presented by Intesys.