Today was a day to catch up a bit. Are you going into the weekend feeling behind, or relatively on top of things? I’ll gift you a shorter reading list today so that I don’t mess up your todo list.
[blog] Test Failures Should Be Actionable. Short post, but an important point. Do you write tests this way?
[blog] How Google’s AI model Gemini got its name. I like this story, as it’s fun to see the background behind a name that will last.
[blog] The #1 Platform Engineering Problem You’ve Never Heard Of: Platform Decay. There is a lot written about setting up a platform, but much less about keeping it healthy over time. This post tries to address the latter.
[article] Use Active Listening to Help a Colleague Make a Hard Decision. Many of us like to jump in and solve problems in front of us, but it’s often better to be a better listener. Here are four types of active listening support.
[blog] 100 things we announced at I/O 2024. Here’s a good list to skim to see what’s available now, and coming soon, in the consumer and builder space.
[blog] To tune or not to tune? A guide to leveraging your data with LLMs. Today, there are a handful of valid ways to get better responses from an LLM. There might be more tomorrow! But for now, how do you decide among current options? This post has a useful breakdown.
[article] AI coding tools are your interns, not your replacement. I think AI assistants for devs are more helpful to junior folks than other might believe. But I get the various perspectives shared in this article.
##
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 
Leave a comment