

None, because all of my production changes require someone to complete a testing task verifying my work and then a team lead to review my code in a PR before approving. For certain apps, there’s more extensive UAT required as well. Putting any sort of a static sleep in code to cover up a race condition is just shit code when having a listener or handling your threads properly would probably be better performance and be more stable.
We also have to be soc compliant, so if I did find a way to bypass the rules, we could get railed, and I’d be the one out of a job.



I don’t really understand why voting machines are complicated enough that there are feasible vulnerabilities. They have one job, and it’s to count. It really shouldn’t be too tough for a crack team of competent devs to write the software required to make them work securely. No network access, a memory safe language, and strict business rules should be relatively trivial to setup. Double that will external audits and you’ve got yourself a stew.