Link to Original Source
If we have a machine-readable and human readable paper record, then the paper record could be imaged, then submitted to a independent system to verify that all the votes are accounted for, and that what is printed is what is read by machine. It is up to the voter to verify what is printed is what was voted.
What's more is the voting verification system does not need to be from the same manufacturer of the voting machine itself.
Without a doubt, web is s crapshoot of browser inconsistency and standards. Imagine this hypothetical scenario: No more local apps, but you have a web server running locally, which when you install an app, installs to the local web server. Your entire desktop is in a browser. What are the problems with this? Many: 1. Serialization to HTML/CSS/JS is slow and unnecessary. The code path to put a red rectangle on the screen is absurd 2. Those interfaces prevent direct access to local hardware. 3. Operational Latency - the back and forth across the web-client/web server barrier is prohibitive for many apps. 4. Start-up Latency - downloading 3D textures and meshes and other assets can take hours.
What is more likely to happen is we have local clients that use web content within the local client.
And then there is the"fog". I call private clouds the "fog" because it's around you, not up in the sky. The web does have the ease of software distribution on it's side. I think eventually when all this NSA stuff shakes out, we'll move to local clouds with self-hosted data as a way to protect and manage our data. There will be an industry standard super server you install apps to which will mimic local apps. Then for your data to be accessed rather than serve a warrant to your hosting provider, they have to serve the warrant to you directly.
Really, I see the privacy and 3D (coming virtual reality) to bring back focus on local apps.
I'm showing my age here, 38, but no talk is complete without mentioning the Dunning-Kruger Effect. I have witnessed this first hand, even with myself. When you are young and full of vigor, you charge forth into the great unknown t eagerly writing lots of code. As you gain experience the code decreases but is of higher quality. I've now taken to assign a valuation to each line of code as liability vs added value. because in a few years some kid will come behind me other the other side of Dunning-Kruger and change this without really knowing what it is doing. I also spend more time doing research on what I am doing so my execution is flawless. Experimentation is rare. In the Art of war, the battle is only the last step and the preparation is really what determines the outcome. Similarly, code is only written when the planning is complete. This is the difference between code monkeys and engineers.
But older engineers often get complacent. I too went through this phase. Many get comfortable with one technology, (Java,
My advice is if you're old, don't get complacent, keep learning. If you're interviewing one of us veterans, keep an open mind. We might not be as cheap on paper, or outwardly enthusiastic. But if we're still in it after 20 years, we love what we do just as much as a new guy, and we will pay dividends in the long run.