The four-year-old typo that nobody can fix 🧟 and more about building developer tools

As the host of Making Software I get to have some pretty real conversations about what it actually takes to build good software. And in my recent chat with Raghd Hamzeh (Senior Software Engineer at Okta and a core maintainer of OpenFGA ) hit home for me. We talked about a side of engineering that doesn’t get enough airtime: what happens when your users are other engineers? If you’ve ever built an API, an SDK, or even just a shared library, you know that developers are the most rewarding, but also the most "vocal" audience you can have. Here are the three things from our conversation that have been living rent-free in my head: 1. The "Breaking Change" Itch is Real 😬 Raghd admitted something that I think a lot of us can relate to: when there’s a four-year-old typo in one of the products you're building, that drives you crazy. It could be just a small naming inconsistency, but when it’s there , it's staring back at you every time. We got into that internal battle every maintainer knows: d