Kubernetes and machine learning content today. That’s my life now. You’ll also find some other great stuff in the mix.
[blog] No Time To Lead? Then Be Prepared To Fail. This is an important perspective, and definitely a major risk with the player/coach model. If you’re not investing in leadership activities, you’re hurting the team.
[article] AI is my copilot: The promise, and perils, of AI code generation. For now, it’s wise to treat AI assistants as a slightly-drunk knowledgeable friend. They may offer some great advice, but don’t always trust it.
[blog] Sharing the inaugural State of Kubernetes Cost Optimization report. This is a solid report that should tangibly help you reduce cost, while understanding what “optimized” looks like for Kubernetes workloads.
[blog] Improve system resiliency using Failure Mode and Effects Analysis. How the McDonalds team thinks about resilience engineering.
[blog] GKE Security Posture dashboard now generally available with enhanced features. Do you have a good handle on the security risks and applicable security bulletins for your Kubernetes clusters? If yes, then you’re very special. If not, you might like that GKE now turns this new service on by default, for free.
[blog] Running Wasm in a container. My colleague Mete has been digging into Web Assembly, and this is his next post. It’ll be interesting to see if folks combine containers and Wasm in the real world.
[blog] Building Real-time Machine Learning Foundations at Lyft. Here’s a look at some of the data pipelines and processes Lyft set up to have more timely ML recommendations.
[blog] A few words on taking notes. Are you a note taker? Here’s how AWS CTO Werner does it.
[blog] Announcing the first Machine Unlearning Challenge. Can you make an ML model forget, or “unlearn”, data? This challenge is going to find out.
##
Want to get this update sent to you every day? Subscribe to my RSS feed or subscribe via email below:
Richard Seroter's Architecture Musings 
10 years after I first heard the about Docker, I am still trying to understand a business case for containers. Somebody said it’s about simplicity – and then went on for 30 minutes about Docker, Kubernetes, registries, and on and on and on!
What do you need containers for that cannot equally well be done with regular instances? Seems like a solution in search of a problem.