So, many unchecked computer programmers at different levels writing software code that almost no one visually inspects or rigorously tests for nefarious content after they load vendor and locally written election ballot software immediately preceding each election. Local election officials and every U.S. citizen can only trust that each member of the small army of computer programmers who writes code destined to run on each and every DRE voting machine and central tabulator computer do not act on partisan political motivations to stuff the software ballot box. It would be so easy for a political partisan to entice or plant a few willing temporary contractor programmers in key election jurisdictions to stuff the software ballot box as they perform their legitimate programming duties. Even just a few motivated partisan programmers each working independently could easily throw an election into even deeper chaos than happen in Palm Beach County FL in November 2000 with rigged punch card ballots.
In the final analysis, software and ballot integrity issues surrounding DRE eVoting machines are so pervasive that, even if updated to print a paper audit ballot, they are just too complex and costly to resolve in any fully transparent election process.
Speaking as one of those 479,640 Election Judges who conducted the November 2006 election on DRE eVoting machines, I shudder to think of the chaos balky add-on ballot printers might inflict on the election process. Can you imagine the chaos and cost of fixing broken ballot printers, changing empty ink cartridges and paper rolls in a busy polling place with voters waiting in line one hour, two hours, three hours to vote? Remember, most citizen election volunteers are over the age of 70 and retired – could your grandmother tame a balky ballot printer?
(Note: You can view every article as one long page if you sign up as an Advocate Member, or higher).