I found a lot of good advice in today’s reading. There was useful perspective on how to think about the value of AI assistance, tips for asynchronous systems, how to build an effective incident program, and how to write good docs. Dig in!
[article] AI and the future of software development. Many folks are focused on AI generating code, but Matt points out that understanding code, or reviewing code, might be where we’ll find significant impact from LLMs.
[blog] Serverless take the wheel. Simple post, but good reminder that fully managed services continue us on a journey of offloading plumbing work and focusing on the good stuff.
[blog] PRESTO – A multilingual dataset for parsing realistic task-oriented dialogues. Cool stuff from Google Research. Read about the problem with task-oriented dialog, and click through to the downloadable dataset.
[blog] Don’t Fail Publishing Events! When dealing with message brokers and databases, you need to think through a variety of scenarios. What happens if publishing fails? Should you write to the database FIRST? This post explores the topic.
[blog] How to transition your career into an in-demand cloud role with suggested job paths. It’s a terrific time to invest in a career in the cloud. Priyanka has a useful post for some learning journeys.
[blog] How We Keep Our Government Apps Running With High Reliability: A Peek at Our Incident Management Strategy. Elevate the advice you see from practitioners, and moderate the advice you take from vendor goons like me. This is an insightful look at a real-world incident management process from people who live it.
[blog] Best and Worst Practices in Technical Documentation. Docs aren’t an afterthought. At least they shouldn’t be! This post has applicable advice for those trying to create or improve their documentation.
[blog] The difference between libraries and frameworks. Are you using these words in the right way? I do not. This post reminded me to tighten up my language and not use certain words interchangeably.
[article] Getting Developer Self-Service Right. Read this, and ask yourself if you’d fall into the high-performing or low-performing team bucket, and react accordingly.
##
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 
One thought