Last week I wrote about saying no to a feature request: a user designed a laneId mode for my project over four days, and the right answer turned out to be zero lines of code, because they ended up shipping the fix themselves — in their own layer.
That post was accurate. The decision was right. The code that shipped was right.
The explanation I gave them for why a particular setup would work — the one I wrote with full confidence, in public, on the issue thread — was wrong. Not completely wrong. Wrong in the more embarrassing way: one layer off.
They caught it within a day of my closing reply.
The claim
