Gereon Hermkes

The episode delivers several substantive ideas about deployment as a competitive advantage and the psychology of deployment delays, but relies heavily on extended analogies (e-commerce warehouse, train switches) that consume time without proportionally adding new insights. Core ideas - frequent deployment enables faster learning, waiting makes deployments harder, automation improves both speed and quality - are solid but not densely packed; there's considerable repetition and throat-clearing around the Amazon example.

“The longer you wait, the more difficult the deployments will get.”

“If you deploy every two weeks because you have invested in the systems, you won't have that problem.”

The core argument - that deployment infrastructure is a competitive moat and that frequent deployment beats infrequent deployment - is well-reasoned but not particularly novel in DevOps circles; it echoes established thinking from Amazon, Netflix, and continuous deployment advocates. The analogy to e-commerce warehouses and train automation is illustrative but represents repackaging rather than fresh thinking. The psychological trap of waiting to batch deployments is the most original contribution here, though even that is familiar to practitioners.

“You can have as many scrum teams as you want. If you're not deploying, you don't have business agility.”

“By implementing DevOps...you're actually not only getting quicker, your quality is actually going up as well.”

This is a solo monologue by the host, Gereon Hermkes, promoting his own book. There is no guest, no practitioner being interviewed, no dialogue, and no external perspective. This is purely author self-promotion masquerading as a podcast episode.

“This podcast is a companion to the book I have written with Louis Cantella”

The episode cites Amazon, Facebook, and Google as examples of fast deployers and mentions Amazon deploys several times per second, but provides no concrete data, metrics, timelines, or named case studies from real deployments. The infrastructure cost estimate ("less than a million euros or dollars") lacks sourcing or specificity. Most claims rest on logic rather than evidence; no numbers on deployment frequency improvements, failure rates, or business outcomes are provided.

“Amazon actually deploys their software several times a second”

“the infrastructure setting it up is going to cost less than a million euros or dollars”

There is no conversation. This is a 17-minute monologue with no host-guest interaction, no follow-up questions, no pushback, no challenge, and no dynamic dialogue. The host speaks uninterrupted; there is no one to ask sharp questions or push back on claims. This format precludes any assessment of conversational craft.

“Thank you for listening to that episode.”