이 에피소드에 관해

영어
미국

전사 🔗

과거 에피소드 검색

DevOps Paradox의 과거 에피소드를 검색하세요.

이 팟캐스트의 다른 에피소드

#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](…
#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…
#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…
#365: A bad engineer with a laptop is much worse than a bad engineer with a calculator. Now hand that engineer AI. DORA's ROI report puts it politely - AI without engineering excellence just scales your problems. Except it's not more of everything. It's more of whatever you were already doing, and…
면책 조항: 이 페이지에 포함된 팟캐스트와 작품은 Darin Pope & Viktor Farcic에서 가져온 것입니다. 이 팟캐스트는 소유자의 재산이며 Listen Notes, Inc.와 제휴하거나 보증하지 않습니다.