The top things I have read this week 🏆
Week 27 / 2026
Hey there! Welcome to a new edition of Hybrid Hacker! 🌟
Every week I share the top articles I have found and personally read on the internet. I only share the stuff I believe it’s worth your time.
100% signal, 0% slop.
I mainly read things from my public daily digest, which curates an ever growing list of sources. Here is this week’s best stuff 👇
Meet your AI Co-workers for On-call Engineering ⏰
This week’s newsletter is brought to you by our friends at Glean!
Your on-call team shouldn’t spend the first 30 minutes hunting for context.
Glean’s agents act like AI coworkers inside tools like Slack, Jira, and Teams: they read runbooks, trace alerts, explore root-cause hypotheses, and draft fixes while tagging the right owner.
Each agent has its own governed identity, memory, audit trail, and kill switch, so teams can automate critical work without losing control.
🌀 Introducing the Tolaria Alliance! 🦸♂️
9 min • by Luca Rossi
This week I wrote about the Tolaria Alliance: four tools I use every day in my AI coding workflow, which are now backing the project and helping me keep it free and open! I am super excited about this!
🥇 The Cost YAGNI Was Never About
4 min • by Kent Beck
I love how Kent reframes YAGNI for the AI era. The cost has never been writing the actual code, but rather spending optionality too early, and pulling investment forward before the feature can pay you back. Great article everyone should read.
🥈 The Wrong Abstraction
4 min • by Sandi Metz
This is a great segue to the Kent’s article above. Duplication is usually cheaper than the wrong abstraction, because the wrong abstraction eventually collects all kinds of bad stuff — parameters, conditionals, and sunk-cost arguments. Sometimes the fastest way forward is going back, but this is usually very hard to do.
🥉 AI and Liability
4 min • by Bruce Schneier
Including this great piece by Bruce even if it’s not properly about software engineering, because it’s so relevant today. Companies should be liable for what their AI agents say and do, just like they are for employees or published content. If your product presents an answer with your logo on it, you should own it, and not use “the model said so” as an escape hatch.
And that’s it for today! If you find this list useful, please share it with your friends!
You can also read the very same things I read every day via this free daily digest 📬
See you next week!
Sincerely 👋
Luca