À PROPOS DE CET ÉPISODE

Anglais
États-Unis

TRANSCRIPTION 🔗

RECHERCHER LES ÉPISODES PASSÉS

Rechercher les épisodes précédents de DevOps Paradox.

AUTRES ÉPISODES DANS CE PODCAST

#363: Three waves of the web, and you are late for the third one. The 90s were about getting a browser to render your page at all. The early 2000s were about SEO, or as Darin puts it, sell me all the ads ready. Now it is agent ready, and Cloudflare built a scoreboard for it at [isitagentready.com](…
#364: Your CEO comes back from a leadership offsite talking about burnout-proof leadership and AI transformation at scale. Two weeks later you're working through lunch, you're working through dinner, and Slack never stops. Deployment frequency is up. Incidents are up worse. So who was that program…
#360: Assume your production systems go sideways at 3:00am. Your phone doesn't ring. You wake up to a clean incident report - the system caught the problem, fixed itself, and left a Slack note saying it handled things at 3:15. Would you trust it? Viktor wouldn't, not at first. Same as a new hire, a…
#361: Picture a 6,000-line pull request landing in your project from someone you've never heard of. Every test passes - yours, theirs, all of it. And you can tell it was generated. Not assisted. Generated. What do you do with it? Viktor's first move is to poke the premise: how do you even know it w…
#362: Feature flags or canary deployments - do you need both? Viktor puts it to Alex Casalboni from Unleash, who says he argues about this with his colleagues roughly every day, and the answer lands clean. Switching a hostname, a database, an API vendor? That is infrastructure, nothing to do with w…
Avertissement: Le podcast et les illustrations intégrés sur cette page proviennent de Darin Pope & Viktor Farcic, qui est la propriété de son propriétaire et n'est ni affilié ni approuvé par Listen Notes, Inc.