Notes (63)
Why 'be conservative in what you send, liberal in what you accept' still shapes APIs and parsers, and where it breaks.
Why velocity, coverage targets, and badly written OKRs invite gaming once they become the scoreboard.
Hunt and Thomas on why duplicated knowledge is a maintenance tax, and when merging similar code makes change harder.