Writing

Arguments, not announcements

We build a product with strong opinions about how work should be tracked, and the reasoning behind those opinions is more useful than the feature list. These are the arguments — including the parts where the trade-off is real.

More on the way — on why your overdue list belongs at the bottom of the screen, on treating missing data as undefined rather than zero, and on why handover documents were always going to be 40% complete.