why can't the banks just reverse all the transactions?
Imagine you're running a business. A person you've never heard of (let alone met) calls you up wanting a load of expensive stuff. Fortunately one of your employees has a brain and suggests you get payment in advance. Many many dollarpounds land in your account, and you release the order.
As the truck pulls out of the gate, PYNHO(LAM) hits ctrl-Z and the progress bar starts running from right to left...
I vaguely remember something similar but much more recent. IIRC the thing had proprietary interconnects between the modules, to which my reaction was "nah".
Why are people arguing about *units*? The important thing is that if it had been a free-orbiting MURCAN satellite it would have had a gun with the safety off and one under the hammer and no goddam commie particle would have dared to go near it because NUMBER ONE, YAY!
All mechanical representations of decimal numbers potentially lead to inaccuracies.
There, I fixed his poorly worded statement. Now you are definitely wrong.
Yeah, it's not like adding two words to a sentence changes the meaning at all. *eyeroll*.
Another thing. "All" and "potentially" don't really mix well, given that one is an absolute and the other is a weasel word.
Your ignorance is a time bomb waiting to go off.
Given that I'm basically stating the reasoning behind things designed before I was even born, which are still in daily use today, I'm not diving for cover just yet.
When people claim that they need big decimal number types, they're not counting whole eggs in refrigerators.
No, they're counting whole pennies/cents in invoices and bank accounts. Nonetheless, when the thing is intrinsically an integer storing it as an integer involves precisely zero loss of precision, which is what you or some other asshat claimed.
Single precision floating point or even 16-bit integers would do a completely equivalent job at that.
Floating point wouldn't, because the way it rounds is a) different to conventions established before floating point was common and b) because the precision varies depending on the value stored.
Integers might, but you'd have to handle the decimal places yourself, with frigs and bodges as I mentioned in a prior post.
Do you think they invented these things just to be contrary? Really?
1,650,763.73 wavelengths of th eight given off by burning Krypton 86 or the distance light travels in 1/299 792 458 seconds is every bit as arbireary as grains of barley in a row.
Because it's a big number it's fair? I was under the impression that to assess that at least one other number was needed.
Do you try to minimize your tax burden? Do you take any deductions? Are others not allowed to because they made more money?
Yes, yes, no. We're not talking about a plumber getting a deduction for his van, a contractor working out of town claiming his hotel, or an engineering firm building a new R&D lab.
We're talking ridiculously convoluted transactions that have nothing to do with reality and exist solely for scamming the public.
In my first proper programming job the standard was four spaces. Beurk! You run out of space more easily (some old systems limit you to 80 chars because punch cards) and I find it more jarring to read.
If you can't see a two space indent you should let your dog do the typing.
The right way is that (petty cash aside) you don't pay anything that doesn't have an invoice. You wouldn't have an invoice if there's no purchase order. You might also have a delivery note, in which case you'd check the quantities match at least approximately. And you wouldn't have any of the above if there's no vendor master. The vendor master contains the account details to pay into.
You split the task up so it takes at least two people (ideally three) to do all the steps above.
Of course that's not agile or webspeed enough for millenials, which is why fuckups happen.
Hipsters and millenials aren't the same thing. They sure as hell aren't mutually exclusive though.
The first one is almost excusable since it was actually wrong in the groaniad article.
I say almost, since it took me about a second to spot it. You'd think that if EditorManishHD had spent a few minutes reading it he'd have spotted it.
Imagine you're running a business. A person you've never heard of (let alone met) calls you up wanting a load of expensive stuff. Fortunately one of your employees has a brain and suggests you get payment in advance. Many many dollarpounds land in your account, and you release the order.
As the truck pulls out of the gate, PYNHO(LAM) hits ctrl-Z and the progress bar starts running from right to left ...
I vaguely remember something similar but much more recent. IIRC the thing had proprietary interconnects between the modules, to which my reaction was "nah".
His "real" userid is roman_mir. He only uses the other one when his karma's so far down the shitter he gets blocked from posting.
Why are people arguing about *units*? The important thing is that if it had been a free-orbiting MURCAN satellite it would have had a gun with the safety off and one under the hammer and no goddam commie particle would have dared to go near it because NUMBER ONE, YAY!
Yeah, it's not like adding two words to a sentence changes the meaning at all. *eyeroll*.
Another thing. "All" and "potentially" don't really mix well, given that one is an absolute and the other is a weasel word.
Given that I'm basically stating the reasoning behind things designed before I was even born, which are still in daily use today, I'm not diving for cover just yet.
No, they're counting whole pennies/cents in invoices and bank accounts. Nonetheless, when the thing is intrinsically an integer storing it as an integer involves precisely zero loss of precision, which is what you or some other asshat claimed.
Floating point wouldn't, because the way it rounds is a) different to conventions established before floating point was common and b) because the precision varies depending on the value stored.
Integers might, but you'd have to handle the decimal places yourself, with frigs and bodges as I mentioned in a prior post.
Do you think they invented these things just to be contrary? Really?
I don't know that.
[flies up into the air]
Aaaaaaaargh!
My initial instinct was to resist but I'm induced to put aside our potential differences, even if it means doing a complete volte-face.
Assuming it's to the nearest centimetre that's still less than half an inch of spread. 16 is the nearest whole number.
No idea where you pulled 14-18 from.
True. But it's much more consistent.
Because it's a big number it's fair? I was under the impression that to assess that at least one other number was needed.
Yes, yes, no. We're not talking about a plumber getting a deduction for his van, a contractor working out of town claiming his hotel, or an engineering firm building a new R&D lab.
We're talking ridiculously convoluted transactions that have nothing to do with reality and exist solely for scamming the public.
In my first proper programming job the standard was four spaces. Beurk! You run out of space more easily (some old systems limit you to 80 chars because punch cards) and I find it more jarring to read.
If you can't see a two space indent you should let your dog do the typing.
I do. I find the rat-atat-rat-atat-rat-atat-rat-atat very therapeutic.
He can't hear you at the bottom of that hole he's digging.
Yo dawg, I herd u like totally failing...
You can if you have an orbital sander.
Where did you get your MBA? I was thinking I might like to not enroll there.
Day word, cottonmouth. Command word, trinity. Action word, Jericho.
I think DeVry need to update their course materials.
https://en.wikipedia.org/wiki/...
Especially a gipsy one.
I've worked on accounts payable systems.
The right way is that (petty cash aside) you don't pay anything that doesn't have an invoice. You wouldn't have an invoice if there's no purchase order. You might also have a delivery note, in which case you'd check the quantities match at least approximately. And you wouldn't have any of the above if there's no vendor master. The vendor master contains the account details to pay into.
You split the task up so it takes at least two people (ideally three) to do all the steps above.
Of course that's not agile or webspeed enough for millenials, which is why fuckups happen.
Son'y be dillt, I;n usibh ome rifht niw.
Brilliant idea. Until there's an earthquake.