The People Behind Your Favorite Apps

The episode covers familiar QA/testing territory - agile vs. waterfall tradeoffs, shift-left, collective accountability - with only occasional mildly interesting framings (e.g. agile as a 'free pass,' SDLC naming constraining thinking). A large portion of runtime is consumed by host anecdotes and throat-clearing rather than practitioner insight.

“it's almost as if agile has given people a free pass, you know, because we deliver fixes so quickly, because the next iteration is coming out. It's it's almost at the expense of software quality”

“I think I think we're almost strangled by SDLC. The fact that it's called software development life cycle leads people to think that, you know, it's it's all around the developers”

The episode recycles well-established software quality discourse - shift-left, testathons, bug bounties, 'skin in the game,' collective accountability - without offering genuinely contrarian or first-principles arguments. The 'make quality cool' framing is the nominal hook but doesn't yield fresh conceptual ground.

“making it cool again and making it more exciting with these bug bounties that you see these days, and the hackathons that now involved testers they call test athons”

“changing the UZZ and them into a wee because it's it's we collectively that that delivered the software”

Raisa Mohammed is a credible technology executive with genuine dual-sided experience (producer and consumer of software) at a multi-region tech firm, and she has a real development background. However, she is not a widely recognised practitioner or industry luminary, and her organisation is not a recognisable reference point for most B2B listeners.

“I'm Raya Mohammed, technology executive at Bajuan Cybertech. Where a technology company that's headquartered out of the Middle East North Africa region with offices globally”

“I come from a development background. I'm a techie, hardcore checky, right, so I know the mindset that comes with that as well”

The episode relies almost entirely on abstraction. The two most concrete references - a Starbucks POS outage and an automotive airbag sensor recall - are unnamed, unverified, and rounded to vague approximations. No actual metrics, timelines, company names, or dollar figures are cited with precision.

“the famous story is a Starbucks. You know, their point of sales system went down and they had lost out I think a couple of million dollars in sales”

“a very well known automotive manufacturer who had a recall of I think a couple of million cars because there was a software defect on one of their air bag senses”

The hosts ask reasonably structured questions but repeatedly hijack the conversation with extended personal anecdotes (the Michael Bolton course story, the marketing fail-of-the-month tangent, the email signature story), consuming significant runtime. There is no meaningful pushback or challenge to any claim made by the guest, making it a friendly PR-adjacent chat rather than a probing interview.

“I got was lucky enough to take part in Michael Bolton's three day rapid software testing course and it was just amazing that it was just an zing three days of like learning how to be a really great tester”

“one of them is like the failure of like the marketing fail of the month, and people are really reluctant to contribute one”