@juliabreeden
Reflections on software engineering, and writing things I wish I'd understood earlier.
Nothing here yet.
Nothing here yet.
Note: After I reported and investigated the issue described in this post, Apideck published a guide outlining the issue and recommended mitigation strategies. If you’re looking for a practical reference, you can find it here. Part 1: The Problem Cont...

At the beginning of 2025, I ran into a “bug” (caught before PRed!) that forced me to rethink what “type safety” actually means in a dynamic code path. My code was working, the data was correct, and the TS linter wasn’t yelling at me. The problem was ...
