That’s a wrap on this week. I’m ready for a long weekend here in the States, and will be back with a reading list next Tuesday.
[blog] The Incumbents Are Coming. I’m probably in the minority, but I like when staggering leaders roar back into a primary position against the feisty challenger.
[blog] Your Agent Doesn’t Know How to Wait. Huh. I don’t think I’ve come across this idea before. If your agent needs to wait for an operation to finish, make sure you design it correctly. Otherwise, your costs can quickly balloon.
[blog] How to Handle Errors in Go. Whether you’re writing it yourself or asking an AI agent to do it, make sure your code has robust error handling.
[article] Research: How Curveball Questions Can Surface the Insight You’re Looking For. I’ve spent a fair amount of time this year working on asking better questions. I liked this perspective.
[article] How does developer experience shape the way teams use coding agents? From this data, it looks like those with more experience in a project apply more careful use of AI, and with more rigor.
[blog] Stop rebuilding from scratch: cache Docker layers on Cloud Build. These numbers can have a big impact at scale. Great deep dive here.
[blog] Portal by Spotify cut my Claude Code token usage by 90%. Wasting a ton of tokens just having your LLM read files and do I/O tasks? Save the LLM for real reasoning work.
[blog] How to Think About Open Weight Models. Excellent analysis from Steve here. If you’ve only kept a casual eye on the open model space, or even if you’ve paid close attention, you can learn something here.
[article] Twenty Years of jQuery: How a Little Library Rewired Web Development. This was a big deal twenty years ago. My how everything has gotten more complicated since then.
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