I have noted that when I backup my collection (which we all do regularly, right?) the overall progress shows 88% when the profiles have been backed up and the backup of cover scans starts. I always wondered what algorithm Ken used that comes to that conclusion. 

That's not really important, but it does remind me of an old developer saying: "When you're 90% done, half the work remains." What that means is that you always underestimate the time it takes to test, correct, test again, etc.

And, if you're anything like me, there will usually be very late realizations during testing, such as "Oh, it would be better if it was done like this", "Ah, we need to be able to configure that", "Hm, that user interface looks a bit awkward. I should fix that", "Wait, I should add such-and-such feature!"

And then you need to document the stuff (fun, fun, fun ). So when you have coded 90%, you think you're almost done, but you really aren't.

PS. "An old developer saying" means that the saying is old, not the developer. Or does it ...?