We are on the same side. We want the numbers to be right, why not? First, the coding needs fixing - the first link, at first look, shows 0 0 0. Broken. When it is fixed, we will all rally round to get all the numbers sorted, based on what solution the coder creates. Meanwhile, less is more.
Coders/Developers can be a funny lot. Almost as bad as mechanics sucking the air over their teeth as some sort of universal signal meaning:
"This will take forever and cost you as much as I can get out of you"
in response to your exasperated exclamation of:
"I don't know what's wrong with it, it it's not working. You're the mechanic. It's your job to find out what's wrong, and fix it."
With developers it's usually best to have a clear idea of how you want something to work, and what you want it to look like in the end, before you get started. Providing them with clear specification documents stating user requirements and acceptance criteria. Even mocking up a process flow diagram explaining exactly how the procedure should work. Otherwise you can go round and round in circles for a long time.
The difference between a Car Mechanic and a Developer, is that if we don't know what it's supposed to do, then the developer wont know either.