Daily Reading List – June 8, 2023 (#106)

Tomorrow I’m heading off on vacation for a full week of no news, email, chats, or work-related things. Scary! The next issue of this daily reading list will come on June 20th. Read slowly until then!

[blog] The Modernization Imperative: Shifting left is for suckers. Shift down instead. New from me! We need to find ways to stop shoving more onto developers’ plates in the name of “shifting left.”

[article] Build a Strong Learning Culture on Your Team. Your team or company success won’t be dependent on adopting a particular technology or product. It’ll likely be solely based on how well—and how quickly—your team learns and adapts to things around them.

[blog] Ten ways troubleshooting GKE apps is now easier in Cloud Logging, part 1. Application logs are a powerful part of your troubleshooting toolbox, but sifting through piles of data isn’t a ton of fun. I like these updates to our Cloud Logging experience.

[blog] Crash Course on Go Generics. Good look at how to use this relatively new feature of the Go language.

[article] Google’s Bard AI is getting better at programming. Yes, yes it is. Math too. The rate of improvement to our models and experiences is remarkable. Fun times.

[article] Building StarCoder, an Open Source LLM Alternative. This model caught some attention, and I learned a few things by reading this.

[blog] Document AI: Understanding invoices to passports and beyond. All these underlying AI models are amazing, but what matters is the interfaces into them. Here’s a look at modern document processing.

[article] CIOs torn between innovation and optimization. It’s a polarity more than a “this or that” choice, but I’m sure it’s difficult right now to balance the need for both.

[blog] Introducing Google’s Secure AI Framework. Very interesting! We’re kicking off this new framework and offer up some tangible next steps.

[article] How New CEOs Establish Legitimacy. Very good advice for any leader coming into a team and trying to establish themselves.

[blog] How to keep your new tool from gathering dust. How many things do you have in your house that you bought with great expectations, and then did … nothing? It happens at work too. This post has useful advice for not letting your new purchase gather dust.

##

Want to get this update sent to you every day? Subscribe to my RSS feed or subscribe via email below:

Author: Richard Seroter

Richard Seroter is currently the Chief Evangelist at Google Cloud and leads the Developer Relations program. He’s also an instructor at Pluralsight, a frequent public speaker, the author of multiple books on software design and development, and a former InfoQ.com editor plus former 12-time Microsoft MVP for cloud. As Chief Evangelist at Google Cloud, Richard leads the team of developer advocates, developer engineers, outbound product managers, and technical writers who ensure that people find, use, and enjoy Google Cloud. Richard maintains a regularly updated blog on topics of architecture and solution design and can be found on Twitter as @rseroter.

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.