It’s a book about computer networking, but deliberately not protocol-first. I’m trying to explain the shape of the system using analogies and mental models first, then map those back onto the real machinery.
That one is about risk management. I’ve been noticing time and time again, in multiple orgs I’ve worked with, that direction and implementation don’t align in many cases. Devs end up doing work that no one asked for, and middle managers tend to “invent” irrelevant work.
This is about learning software architectures using chaos testing. You can bring your own architecture, inject failures in safe environments, practice, and ultimately generate agent skills to automate fixes for these types of failures.
So, I'm building mooomooo, which is my idea of what it means to replace tools like JIRA, linear, and such with a unified data model that can adapt to solo devs, small teams and huge orgs so I don't have to manually move tickets to done.