Yesterday’s list had a pile of good advice, and so does today’s list. Whether it’s doing test-driven development, measuring productivity, thinking about day-2 ops, or making your docs agent-ready, there’s something for everyone.
[blog] Dancing backwards with Go: why TDD is weird. In any language, TDD can feel weird. Writing the failing test first, and then make it pass? I’m not sure how well LLMs comprehensively do it.
[blog] How to measure AI productivity? Still a remarkably important question. You say you’re saving time with AI, but what outcomes changed? Measure the waiting, not just the individual tasks.
[blog] Tokenomics (Or the right tool for the right job). Matching token use to outcomes isn’t easy for anyone. That’s enough to drive a CFO bonkers.
[blog] From Python to Rust, Go, to… Java? Steering Your AI Coding Agent Through Architecture Trade-Offs. Digest what Alexis is showing here. Vague requests to the LLM/agent yield some default languages and architectures that may not match what you really want. Be clear with your app needs so that the “default” language matches your use case.
[blog] Day 2000 Doesn’t Care How Fast You Shipped. Truth. Is your platform helping you maintain and operate all the software you’re delivering?
[blog] 100% of your developers should be building things to improve the workflow. Are they? Is that the case with you, or the place you work? Probably not. But how do we switch our focus to the systems that produce the output?
[blog] The Git Forge for Agent-Human Collaboration. I really like where they’ve landed here. This looks like a legit alternative to traditional git solutions. More here.
[blog] Bringing Google TPUs to Oracle Cloud Infrastructure. Everybody gets a TPU. This valuable processor is getting wider access, and more tools for using it.
[blog] Keeping a software factory stable at 1,000 PRs a week. Build things to improve the workflow, and increase your trust in the system.
[blog] Are agent harnesses dying? What harness distillation changes. Today’s harnesses may be unnecessary in six months. The model will do it. But I’d imagine we’ll want something that sits outside, even for the option to swap models.
[blog] Making documentation pages agent friendly. My team’s doing a lot of work here, and Tom encourages everyone to understand how agents see their docbase.
[blog] Testing and Serving A2A Agents from the Terminal with A2A CLI. Here’s a good walkthrough of this useful tool for interacting with agents over A2A.
[blog] The push to modernize legacy tech. It’s not hard to regenerate code. But you still need a good reason, and must be aware of the risks.
Want to get this update sent to you every day? Subscribe to my RSS feed or subscribe via email below:
Leave a Reply