Reading a quotation...
-
The quotation mentions rebuilding an Excel sheet to some web application. "This process must be as simple and correct as possible." Not "as correct as possible", just correct. If it's any less correct than "correct" it's not correct :laugh: I wonder, if they mention correctness explicitly at this point, does that mean all other points are assumed to be incorrect by default? :~
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
The quotation mentions rebuilding an Excel sheet to some web application. "This process must be as simple and correct as possible." Not "as correct as possible", just correct. If it's any less correct than "correct" it's not correct :laugh: I wonder, if they mention correctness explicitly at this point, does that mean all other points are assumed to be incorrect by default? :~
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
The quotation mentions rebuilding an Excel sheet to some web application. "This process must be as simple and correct as possible." Not "as correct as possible", just correct. If it's any less correct than "correct" it's not correct :laugh: I wonder, if they mention correctness explicitly at this point, does that mean all other points are assumed to be incorrect by default? :~
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
"This process must be as simple [PAUSE] and correct as possible." With the verb form of "correct" rather than the adjective form. :-D
-
"This process must be as simple [PAUSE] and correct as possible." With the verb form of "correct" rather than the adjective form. :-D
What about "and correct if possible"? ;p Or "and correct if you pay extra for our special 'correctness module'" :cool:
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
What about "and correct if possible"? ;p Or "and correct if you pay extra for our special 'correctness module'" :cool:
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
Exactly. "Fix any detected deficiencies when fiscally sound."
-
Exactly. "Fix any detected deficiencies when fiscally sound."
Correctness is a feature, after all ;)
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
The quotation mentions rebuilding an Excel sheet to some web application. "This process must be as simple and correct as possible." Not "as correct as possible", just correct. If it's any less correct than "correct" it's not correct :laugh: I wonder, if they mention correctness explicitly at this point, does that mean all other points are assumed to be incorrect by default? :~
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
Correctness is a feature, after all ;)
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
Correctness costs money and hinders performance.
-
I've actually had a customer who wanted VAT on invoices calculated per product, which was completely irrelevant, instead of over the complete invoice. The problem is, you're going to round VAT to two decimals, because no one ever pays €0.001. So by adding up all the VATs for each product we got rounding errors (and those rounding errors added up!). If you calculated the VAT over the entire invoice (like EVERYBODY in that business does) it wouldn't add up. But for some reason they really wanted to have the VAT per product. We went as far as to round to 16 decimal places, but we still ended up with rounding errors :laugh: Ultimately, we actually went for "as correct as possible with x decimal places." In this case "correct" was of course VAT over the entire invoice because that was the only legal kind of VAT :laugh:
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
I've actually had a customer who wanted VAT on invoices calculated per product, which was completely irrelevant, instead of over the complete invoice. The problem is, you're going to round VAT to two decimals, because no one ever pays €0.001. So by adding up all the VATs for each product we got rounding errors (and those rounding errors added up!). If you calculated the VAT over the entire invoice (like EVERYBODY in that business does) it wouldn't add up. But for some reason they really wanted to have the VAT per product. We went as far as to round to 16 decimal places, but we still ended up with rounding errors :laugh: Ultimately, we actually went for "as correct as possible with x decimal places." In this case "correct" was of course VAT over the entire invoice because that was the only legal kind of VAT :laugh:
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
Those little bits can add up :) Here if a product is marked as 4.99 you'll pay 4.95 at the till / cashier, due to us no longer having 2c coins. AFAIK the rounding is only done on the total, but if you wanted to save a few cents you could pay for each product individually.
-
I've actually had a customer who wanted VAT on invoices calculated per product, which was completely irrelevant, instead of over the complete invoice. The problem is, you're going to round VAT to two decimals, because no one ever pays €0.001. So by adding up all the VATs for each product we got rounding errors (and those rounding errors added up!). If you calculated the VAT over the entire invoice (like EVERYBODY in that business does) it wouldn't add up. But for some reason they really wanted to have the VAT per product. We went as far as to round to 16 decimal places, but we still ended up with rounding errors :laugh: Ultimately, we actually went for "as correct as possible with x decimal places." In this case "correct" was of course VAT over the entire invoice because that was the only legal kind of VAT :laugh:
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
At least in the UK, it's perfectly fine to do it either way: 17.5 Calculation of VAT on invoices - rounding of amounts[^] Calculating per line makes it easier to deal with invoices where different products attract different VAT rates. And if you calculate and round per line, you sometimes end up paying slightly less VAT. :)
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
The quotation mentions rebuilding an Excel sheet to some web application. "This process must be as simple and correct as possible." Not "as correct as possible", just correct. If it's any less correct than "correct" it's not correct :laugh: I wonder, if they mention correctness explicitly at this point, does that mean all other points are assumed to be incorrect by default? :~
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
Sander Rossel wrote:
If it's any less correct than "correct" it's not correct
That is the most true statement I've ever read.
Social Media - A platform that makes it easier for the crazies to find each other. Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
-
At least in the UK, it's perfectly fine to do it either way: 17.5 Calculation of VAT on invoices - rounding of amounts[^] Calculating per line makes it easier to deal with invoices where different products attract different VAT rates. And if you calculate and round per line, you sometimes end up paying slightly less VAT. :)
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
So in practice you could get that new car invoice to be itemised by the atom and because HMRC allows you to round down there would be no VAT to pay :-D
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
-
What about "and correct if possible"? ;p Or "and correct if you pay extra for our special 'correctness module'" :cool:
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
You're starting to sound like EA Games ... DownLoadableCorrectness, anyone?
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony AntiTwitter: @DalekDave is now a follower!
-
So in practice you could get that new car invoice to be itemised by the atom and because HMRC allows you to round down there would be no VAT to pay :-D
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
I have a small feeling HMRC may see it slightly differently ... :~
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony AntiTwitter: @DalekDave is now a follower!
-
The quotation mentions rebuilding an Excel sheet to some web application. "This process must be as simple and correct as possible." Not "as correct as possible", just correct. If it's any less correct than "correct" it's not correct :laugh: I wonder, if they mention correctness explicitly at this point, does that mean all other points are assumed to be incorrect by default? :~
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
The quotation mentions rebuilding an Excel sheet to some web application. "This process must be as simple and correct as possible." Not "as correct as possible", just correct. If it's any less correct than "correct" it's not correct :laugh: I wonder, if they mention correctness explicitly at this point, does that mean all other points are assumed to be incorrect by default? :~
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
Excel does a lot of magic; read theoldnewthing if you want details that you never need. Fun fact; Excel has better VB than the other MS products.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
So in practice you could get that new car invoice to be itemised by the atom and because HMRC allows you to round down there would be no VAT to pay :-D
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
GuyThiebaut wrote:
itemised by the atom
That would be a long invoice. :)
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
-
Those little bits can add up :) Here if a product is marked as 4.99 you'll pay 4.95 at the till / cashier, due to us no longer having 2c coins. AFAIK the rounding is only done on the total, but if you wanted to save a few cents you could pay for each product individually.
-
Those little bits can add up :) Here if a product is marked as 4.99 you'll pay 4.95 at the till / cashier, due to us no longer having 2c coins. AFAIK the rounding is only done on the total, but if you wanted to save a few cents you could pay for each product individually.
Over here, in a store (for example, supermarket), VAT is included in the product price. So 500 gr. (pre-packaged) grapes costs €2.19 incl. VAT. If you buy two packs, you pay €4.38. If you pay cash everything is rounded to 5 cents, so €4.38 would become €4.40, but €4.37 would be €4.35. I can't remember the last time I paid cash at a store :D This particular company sold meat (wholesale), so a customer would order five ribs, but they would pay per kg. The customer gets an estimated price, based on what my customer sent them, then that customer would weigh everything again, and that weight was invoiced. Naturally, you don't know the VAT until the actual invoice. And since the VAT isn't included in the individual prices, like in a supermarket, you really can't do anything other than calculate VAT over the entire invoice :D It's how I invoice too, and pretty much every business in the Netherlands.
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
