#377: Every software company that ever thought about sponsoring KubeCon already sponsors KubeCon. So where does it grow from here? Ask what on the expo floor wasn't AI, and you get two answers: the coffee and the puppy petting area. Meanwhile, a lot of the session rooms were half full. We spent years pushing Kubernetes to be stable and ready for production. It is now. But stable and innovative are rarely the same thing, and if your company only pays for one conference a year, which one gets the ticket? In this episode, Darin and Viktor review KubeCon North America 2026 in Salt Lake City with our friend Whitney Lee. Whitney's contact information: LinkedIn: https://www.linkedin.com/in/whitneylee/ X: https://x.com/wiggitywhitney YouTube channel: Review the podcast on Apple Podcasts: Slack: Connect with us at:
#376: How many secrets can your coding agent reach right now? You gave it a token so it could get work done. It might have passed that token to every agent it spun up. Somewhere along the way, you stopped reading the permission prompts and started clicking allow. At the same time, hardcoding secrets in our code is still the most common answer for how secrets are managed. Developers get paid to close tickets, not to lower risk, and the agents just copy whatever they find in the repo. In this episode, we speak with Dwayne McDaniel, Principal Developer Advocate at GitGuardian, about managing secrets when agents are the ones using them, and why the better answer might be no secrets at all. Dwayne's contact information: LinkedIn: https://www.linkedin.com/in/dwaynemcdaniel/ YouTube channel: Review the podcast on Apple Podcasts: Slack: Connect with us at:
#375: An agent can crank out 200 or 300 lines of code a minute. You can maybe review 40. So who's actually supposed to understand what just got merged? Maybe nobody ever did. Did you really read every line of every PR before AI showed up? Or did you just have the time? Now the junior has an agent, the senior is buried in review, and the job looks a lot more like management than coding. In this episode, Darin and Viktor talk about who's supposed to understand the code once AI writes it, and why that's now the senior engineer's job. YouTube channel: Review the podcast on Apple Podcasts: Slack: Connect with us at: