No. 0501 min read
What mediation taught me about people (not that kind of mediation)
Fourteen years reconciling billing records at Sprint taught me to check what I know before assigning blame.
No. 0331 min read
A bigger sequence number does not mean your missing file arrived, folks. Gaps, repeats and resets need explanations that survive the next restart.
You have a bigger sequence number[1]Ref. 1sequence number rfc-editor.org than you had before, and you're ready to delete the earlier file. I'd hang on to it a little longer.
I want to know who issued the number, what it counts, and when it can start over. Without those answers, comparing two numbers gives me very little evidence that everything earlier arrived.
I would keep the missing range separately from the highest number observed. A single high-water mark cannot tell you both how far you've gotten and which holes remain. Let a newer file automatically close an older gap and you've declared success without learning a goddamn thing about the file you couldn't find.
Record counts need the same care. You can have a complete file sequence made of incomplete files, or a complete file with rejected records[2]Ref. 2records en.wikipedia.org. Sequence continuity proves one property of the transfer; there's still accounting to check. The numbers can line up beautifully while I'm still looking for the damned records.
No. 0501 min read
Fourteen years reconciling billing records at Sprint taught me to check what I know before assigning blame.
No. 0361 min read
Corrupt how, folks?
No. 0341 min read
Your parser rejected the record.
No. 0151 min read
Sprint's D3884 finished early and under budget with no customer service impact.