2 ms·
At least it learned from the training dataset to never fucking format numbers in a way that would be remotely readable to the human eye (like every other fuckin
by cm2187 4y ago
At least it learned from the training dataset to never fucking format numbers in a way that would be remotely readable to the human eye (like every other fucking sql and developer tool on earth). Because 133854113715608.0 is telling me exactly what I need to know.
- jletienne 4y agowait what? that number is so big you know it's wrong. commas in numbers are nightmare to deal with and the .0 lets you know it's a decimal not an integer. If it was formatted like 133,854,113,715,608, you'd be stuck trying to figure out if it possibly meant "133,854,113,715,608" or [133,854,113,715,608] which would be awful. Format numbers in excel or any other reporting tool. lmfao i like your comment. what's miserable to you is a lifesaver for me
- cm2187 4y agoExactly. An average developer thinks "it's just some large number". A business user needs to read the number and make sense of it. And yes, showing 133,854,113,715,608 doesn't make much more sense (though at least I can compare the numbers between them). In this case you would express it in billions and mention you did it (doesn't matter that the underlying calculation is wrong, that's not even the point, none of the other numbers in the page are formatted in a readable way).