Daily Reading List – August 1, 2023 (#133)

Sheesh, August 1st! I know folks tend to say “this year is flying by” but I’ve found ways to slow it down. Specifically, last year I started a routine where at the beginning of every day, I write a quick log of what I did the day before. That four minutes of daily reflection really helped me keep the days from all blurring together.

[blog] Comparing GKE Autopilot cost efficiency to traditional managed Kubernetes. Do your teams try and model cost savings or cost avoidance? it’s not always easy. This post does a good job comparing modes of running Kubernetes and the reasonable cost differences.

[blog] How TDD Seems To Go Against Agility. Are you “agile” if you’re planning a bunch of upfront tests for your code? This post looks at that concern, and addresses it from a different perspective.

[blog] Introducing time-bound key authentication for service accounts. Great feature. I’ve seen temporary credentials in other clouds as well. Consider this pattern in your environment.

[article] Microservices Retrospective – What We Learned (and Didn’t Learn) from Netflix. Here’s a good set of lessons learned from Adrian Cockcroft.

[docs] Aggregate infrastructure availability. The availability of your application depends on the aggregate availability of each component in your stack. These updated Google Cloud docs explain this well.

[blog] Saying No In Open Source. This likely applies to plenty of scenarios beyond open source software, but there are unique challenges in managing something with so many random contributors.

[blog] 10 Tips For Writing Great API Documentation. Docs matter a ton, and the quality of your docs will play a big part on whether anyone uses what you built.

[blog] Cloud Functions for Firebase 2nd gen goes GA and adds support for Python. Lots of new and experienced devs use Firebase for their mobile backend. Now those devs have more powerful compute services at their disposal.

[blog] What Does It Mean To Be Wealthy? The Stoics had some good thoughts on what wealth looks like.

[article] Why software developers prefer DORA metrics. No metrics are perfect, but the DORA ones seem to help teams focus on the right areas.

[blog] 20 Google Cloud Reference Architecture to Start your GCP Architect journey. Give me a good diagram instead of a wall of text! Here are 20 architectures that apply to any cloud.

##

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.