points by nedbat 9 hours ago | 0 comments
When I said I hadn't encountered the detail before, I didn't mean amortization was the detail. I meant the order of operations (pyon's complaint) was the detail.
I think you are being very generous to call his comment "obvious humor". A number of the people in that comment stream missed the humor, and pyon gave no indication (such as a tone indicator) that it was humor.
[–] kazinator 8 hours ago
[–] fyltr 8 hours ago
Well, they do seem to have a sense of humor. The "damn you tricked me" bit reuses your phrasing, yet if the shaming were serious, it would mean they are completely impervious to your arguments.
Pyon read to me as someone more technically than socially skilled, who might have a social circle where it is customary to play the obnoxious expert so that nitpicking is funny rather than aggressive. They may not have registered that this is an inside joke, and what would have landed as lighthearted in their circle ended up hurtful and toxic out in the wild.
Operations can incur some kind of "debt" which a more expensive operation occurring later has to pay for. Or they can be regarded as enjoying something "prepaid" by an earlier expensive operation until the credit runs out and another prepayment has to be made. Possibly, either view can be used to arrive at the same result.
The level of contention on the part of Pyon is disconnected from the level of detail given to "amortized" in the article and based on the false premise that the word "average" implies some kind of order that is contrary to "amortized". (Expert, my foot).
It is factually correct that a an amortized performance is an average, but readers should be aware that it's a special kind of average (not every average is "amortized") and that it is a warning label: an algorithm with performance quoted as amortized possibly exhibits a big latency spike that occurs infrequently.