I'm a programmer, and it is absolutely possible to accidently put in a poorly formed if statement and get the opposite result you want. But not multiple times in states that just so happened to be key swing states. And if it really was an accidental error like that, every D vote would have gotten switched to R and every R vote would have gotten switched to D. Furthermore, every machine, in every county, in every state would have gotten that bug, so ALL votes should have followed that pattern. NOT just the votes that happened to be key races in key swing states.
I wonder how the program changes got past the testing stages?
Systems I have been involved in usually had three levels of testing that all had to pass. The programmer tested it, the analyst tested it and finally the user tested it in a pre-production environment.
At that point the management team would decide whether the change should be moved into production. If they also approved only then the change was made.
You're right about all the various testing. We do the same. IF the code was originally tested and working correctly, without the "bug", it would have made it through the testing. What I do know, is that these machines, by law, aren't allowed to be connected to the internet. That means someone would have to come in and physically upload the bug. Kind of like how those technicians came in with a USB drive during the AZ elections in 2020.
Personally, what I believe, is that these machines worked as intended, and code was written to intentionally switch votes from the get-go
Programmer also...these IDIOTO "officials" seem to want us to believe that it was a coding error...HMMMM????
I thought those "VOTING MACHINES" WERE TO BE CERTIFIED WITH A CERTIFICATE SAYING THEY WERE ACCURATE...the people could "TRUST" the voting machines...NOT!!! 😡😡😡😡
Now, where is the certificate and the company's name that did the evaluation?
I couldn't imagine if they had to code something complicated. They have one job and one job only and it is to be sure a yes vote tallies yes and no tallies no. Votes for one candidate tally for that one and a vote for a different one tallies for that person. After years of supposedly working on that task if they can't do it that must be fraud.
A typo is a human error. Reprogramming voting machines is intentional.
I'm a programmer, and it is absolutely possible to accidently put in a poorly formed if statement and get the opposite result you want. But not multiple times in states that just so happened to be key swing states. And if it really was an accidental error like that, every D vote would have gotten switched to R and every R vote would have gotten switched to D. Furthermore, every machine, in every county, in every state would have gotten that bug, so ALL votes should have followed that pattern. NOT just the votes that happened to be key races in key swing states.
I wonder how the program changes got past the testing stages?
Systems I have been involved in usually had three levels of testing that all had to pass. The programmer tested it, the analyst tested it and finally the user tested it in a pre-production environment.
At that point the management team would decide whether the change should be moved into production. If they also approved only then the change was made.
Easy to get past test stage since it worked just like they wanted!
This lol
You're right about all the various testing. We do the same. IF the code was originally tested and working correctly, without the "bug", it would have made it through the testing. What I do know, is that these machines, by law, aren't allowed to be connected to the internet. That means someone would have to come in and physically upload the bug. Kind of like how those technicians came in with a USB drive during the AZ elections in 2020.
Personally, what I believe, is that these machines worked as intended, and code was written to intentionally switch votes from the get-go
Show us the source code then.
Are you asking me for the source code? Why would I have the code to these machines?
Programmer also...these IDIOTO "officials" seem to want us to believe that it was a coding error...HMMMM????
I thought those "VOTING MACHINES" WERE TO BE CERTIFIED WITH A CERTIFICATE SAYING THEY WERE ACCURATE...the people could "TRUST" the voting machines...NOT!!! 😡😡😡😡
Now, where is the certificate and the company's name that did the evaluation?
That's like the most basic comp sci 101 first things you learn lol
https://greatawakening.win/p/17rlrKEbPa/x/c/4Tz1dOjV0L8
I couldn't imagine if they had to code something complicated. They have one job and one job only and it is to be sure a yes vote tallies yes and no tallies no. Votes for one candidate tally for that one and a vote for a different one tallies for that person. After years of supposedly working on that task if they can't do it that must be fraud.
It’s not human error since they Dems did it on purpose. It was a success not an error.
Exactly and look how many elections this happened in the past and always the vote went to the Democrat.
EVERYONE
CALL TO RESEARCH
Look at the bond-backed propositions in every local election you can find.
They’ve pushed TENS OF BILLIONS in bond proposals out this election cycle, with 500 million dollar bond proposals getting approved by 425 votes.
RESEARCH NEEDED.
THREAD: https://greatawakening.win/p/17rlrMTkE3/