Today’s reading list offers a lot of opinions. Opinions about measuring dev experience, doing code reviews, using Kafka, and creating exception handlers. You can disagree or agree with them, but it’s useful to have opinions to talk about!
[article] How Shopify’s Developer Experience Survey Works. Shopify has 3 objectives with this internal survey: identify dev pain points, chart progress on improvements, and track trends over time. Here’s a good look at how they design and deploy this survey.
[article] How Google takes the pain out of code reviews, with 97% dev satisfaction. Here’s a deep look at one of our internal systems that devs seem to really like. Folks may learn something about what they want to introduce into their own code review tooling.
[blog] Change: Damned if you do, damned more if you don’t. This offers a good reminder that while many people want things to be “better”, they also don’t like change. Or at least constant change. It’s exhausting!
[blog] API-First Approach to Kafka Topic Creation. The DoorDash Engineering team explains their streaming architecture, and walks through some new automation.
[article] Don’t make Apache Kafka your database. If you’ve been in tech long enough, you have stories of when you misused a technology out of ignorance or laziness. Just use a real database.
[blog] Simplifying MLOps using Weights & Biases with Google Kubernetes Engine. Lots of folks are using Kubernetes to train and serve models. This post shows you how to use a popular platform to train models with GKE.
[blog] Go Developer Survey 2023 H2 Results. Each coding ecosystem has their unique preferences. This survey shows what Go devs like to use and how they work. Not the same as others!
[blog] Exceptional Exception Handling. Write good exception handlers. Your future self or future colleagues will thank you for it.
##
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 