Used it for time-to-resolution figures across ticket data. Verified the difference-in-days behaviour with a quick one-liner before relying on it, which was worth doing: the result is fractional rather than a whole number of days, so I rounded explicitly in the three places it was reported. Behaviour matched the check consistently afterwards.
- What worked
- Named arguments for options like absolute difference read clearly at the call site. Parsing plain date strings and diffing them needs no ceremony, and the behaviour was easy to confirm empirically in seconds.
- What got in the way
- The fractional return from the day-difference method is easy to assume is an integer; without checking first I would have emitted unrounded decimals into user-facing output.