Jun 23, 2026 · 51 min · 11 segments
Welcome to **Browser Stack Talks**, the podcast where we turn testing pain points into playbooks. In this episode, host David Burns sits down with Marie Cruz, Senior Developer Advocate at Grafana Labs…
Marie CruzGuest
David BurnsHost
And hopefully at the end, we'll be able to kind of ask you a bit more about that when we get to the quickfire round.
But I think kind of one of the things we should definitely talk about and hasn't really been talked about on this podcast yet is the modern performance engineering mindset.
And he was talking about the maturity model of every company, even from the biggest companies, they tend to get things wrong and without realizing they're getting it wrong.
And so you've been an advocate for moving away from the old test at the very end model.
So that we can clear things up, how do you define the difference between traditional load testing and kind of what is considered modern performance engineering?
And to make it simpler for me, the difference is when and how performance is addressed.
Because if we think about this like traditionally, you know, load testing or performance testing of any kind, you only do it right at the very end.
It was often treated as this final checkpoint of asking, hey, can our system actually handle the expected number of users before You know, we go live and then teams would run a very large test.
There's a lot of talks about like quality engineering, like shift left, shift right, continuous, you know, all those like buzzwords.
And hopefully at the end, we'll be able to kind of ask you a bit more about that when we get to the quickfire round.
But I think kind of one of the things we should definitely talk about and hasn't really been talked about on this podcast yet is the modern performance engineering mindset.
And he was talking about the maturity model of every company, even from the biggest companies, they tend to get things wrong and without realizing they're getting it wrong.
And so you've been an advocate for moving away from the old test at the very end model.
So that we can clear things up, how do you define the difference between traditional load testing and kind of what is considered modern performance engineering?
And to make it simpler for me, the difference is when and how performance is addressed.
Because if we think about this like traditionally, you know, load testing or performance testing of any kind, you only do it right at the very end.
It was often treated as this final checkpoint of asking, hey, can our system actually handle the expected number of users before You know, we go live and then teams would run a very large test.
There's a lot of talks about like quality engineering, like shift left, shift right, continuous, you know, all those like buzzwords.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.
