Daily Wrap Up – January 30, 2023 (#019)

Did you have a good weekend? I was able to meet up for dinner last night with a friend (and blog reader!) and it’s energizing to be around folks who love to learn as much as I do. Today I read a wide range of things that touched on technical writing, coaching, and more.

[blog] Building a Staging Environment for Data Teams. This post offers some guidance for those trying to offer an up-to-date staging environment for data workloads.

[blog] Go migration guide: Node.js, Python, and Rust. You may spend your whole career as a developer working with one programming language. Kudos. I admire that. Others of us decide to pick up a few languages just to spice things up. Read this to learn about switching to Go.

[blog] Technical writing resources. AI robots might be getting good at writing text, but it’s still useful to learn how to document and communicate better. Read this post for links to some very useful assets.

[blog] Do these five things to be “effectively decisive.” I wrote it, so I guess I also read it 🙂 This topic was on my mind yesterday so I shared some quick thoughts on what you need to make decisions quickly.

[article] Women Get “Nicer” Feedback — and It Holds Them Back. This feels true. Unfortunately. Intentions may be good, or this may be entirely subconscious, but we’re not doing anyone a favor by withholding useful feedback.

[blog] Powering Millions of Real-Time Decisions with LyftLearn Serving. Lyft runs a lot of predictive models, and this post explores the system they build to deploy and serve ML models.

[paper] Three Actions Enterprise IT Leaders Can Take to Improve Software Supply Chain Security. Read this new Google Cloud paper today. It’s a good overview. You’ll have to sacrifice your email address, but if you’re in a leadership position and making decisions on software security, I think it’s worth it.

[blog] Top 5 GO REST API Frameworks. I tend to use frameworks instead of the raw language primitives. Some folks skip it, but for many of us, the ease of use is worth it.

[blog] Improved gVisor file system performance for GKE, Cloud Run, App Engine and Cloud Functions. Sometimes you should rewrite things instead of tuning what’s already there. In this post, we talk about the new file system layer we wrote for the gVisor component that protects containerized workloads. Good security and good performance? Yes, please.

##

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 Director of Developer Relations and Outbound Product Management at Google Cloud. 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 Director of Developer Relations and Outbound Product Management, Richard leads an organization of Google Cloud developer advocates, engineers, platform builders, and outbound product managers that help customers find success in their cloud journey. Richard maintains a regularly updated blog on topics of architecture and solution design and can be found on Twitter as @rseroter.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

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