5 ms·
> The parties in the case stipulated a total loss amount of $42,262.50 That's an oddly specific loss amount, especially the 50c
by BuildTheRobots 7y ago
> The parties in the case stipulated a total loss amount of $42,262.50
That's an oddly specific loss amount, especially the 50c
- isoskeles 7y agoWhat’s odd about it being specific? Take the number of billable hours he spent “fixing” his logic bombs x hourly rate for those events.
- dTal 7y agoThe loss also extends to any lost business resulting from the broken code, lost work, time on behalf of the people whose job it was to call him in, etc. These are very difficult to quantify exactly, and so the number of significant figures in the claimed amount looks odd. But the law doesn't allow you to say "oh, about 50 grand", so I imagine significant figure rounding in financial estimates isn't strongly emphasized anyway.
- pc86 7y agoYou have to be specific, as others have mentioned. And it's not that odd: * Contractor's time multiplied by their hourly rate * Whoever was overseeing the contractor for some percentage of their time multiplied by their fully loaded hourly rate * Processing and payment of contractor's invoices * Discounts or coupons given out as a result of late orders due to this problem * Anything in any contract relating to late orders that was caused by this problem, even in part You start multiplying fully loaded employee costs (including 401(k) matches, healthcare, etc) by fractions of a percentage for how often they deal with this person and it's not at all hard to end up with fractions of a penny at the end of it all.