• Spec Driven Development isn’t Waterfall: Writing down precise specs with intended behaviour, trade offs made, and how to test seems like a great artifact to have if it can be readily turned into executable code.
  • Inside Gen 13: how we built our most powerful server yet: Love this server build stuff. Lots of good notes about testing. These guys are deeply familiar with what the hardware can do and what they need it to be able to.
  • Agentic coding at ClickHouse: How clickhouse is currently thinking about ai use. (At least how one of the technical founders thinks about it anyways. :))
  • The Future of Everything is Lies, I Guess: Where Do We Go From Here?: :’( This isn’t a good news blog post but entirely plausible …
  • The post-mortem problem: “ Post mortems have become less of a learning exercise and more of a compliance exercise”. Interesting. I’ve definitely been emphasizing a long timeline of loosely connected, extremely detailed events that happened during an incident and less on the broader strokes and feelings in the moment. My timelines are long, mechanical sounding, and boring … hrm. Emphasized in the article is that post mortems are for humans and learning.
  • The Picture They Paint of You: For developers ai is seen as something that will help you build the next great thing. On the operations side it’s seen as a way to automate away the drudgery. Maybe this isn’t that far off. Operations energy is a way to increase safety, and stability, and awareness of what’s happening in production. It’s not about holding on to old ways of thinking about work …