Flip through the items I read today, and see what stands out to you. I consumed some good perspectives on security, tech experimentation, technical debt, and AI/ML.
[article] Security Needs Create More Work for Open Source Maintainers. It tough to keep up with bug and features requests for open source projects, especially for unpaid maintainers. Security is being left aside by many, according to this data.
[article] The Engineer/Manager Pendulum. Whether you’re an existing manager, aspiring manager, or leader of managers, you should watch this excellent talk (and transcript) from Charity Majors.
[blog] Announcing Cloud Storage FUSE and GKE CSI driver for AI/ML workloads. Now it’s easier to mount object storage buckets as a local file system for Kubernetes pods.
[blog] An ML-based approach to better characterize lung diseases. Real-world problems solved by better analysis of petabytes of data.
[article] How 3 CIOs make time for technology experimentation. From what I’m observing, too many folks aren’t carving up time in their day to just think, or learn. We’re running from urgent thing to urgent thing, without actively managing our time. Here’s a post on CIOs prioritizing experimentation.
[article] GitLab and Google Cloud partner to power generative AI-assisted DevSecOps features. Good to see terrific platforms rely on Google AI to build better user experiences.
[article] New Relic launches Grok, it’s AI observability assistant. AI and operations are going to be great friends.
[blog] Introducing Query plan samples for Cloud Spanner: get performance insights from query execution plans. This looks like a very powerful way to visualize database query execution plans and optimize accordingly.
[blog] When everyone around you is a problem, it’s not them. I’ve thought this before, but never articulated it. But yes, if you somehow see toxic people everywhere, maybe it’s you?
[blog] Effingo: the internal Google copy service moving data at scale. Great name, powerful Google-only service for moving data around.
[blog] “Friction” >> “Debt”. Should we stop referring to “technical debt” and refine our language to talk about removing friction? Good argument here.
[blog] Large-scale User Sequences at Pinterest. Educational read about taking in real-time data and being able to organize it for usage downstream for ML training, and more.
##
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 
One thought