rjmunro
Joined 13 years ago
Joined 13 years ago
In the US, the election is in November and the president doesn't get sworn in until January. It could take a couple of weeks to count the votes and it would be fine.
I think machines are only acceptable if they sort ballots into multiple bins, not if you are using them for the actual count. The bins should be designed so you can casually see that the last ballot to be added is correct for that bin while the machine is working. Something to insert a marker every 100 ballots is probably a good idea, then you can count the number of hundreds, and randomly sample a few of them to check they are correct.
The RISC OS approach is like a million times better. The only thing I would add is a context menu to create a new file of whatever kind at this location, like The "New" menu in windows.
That's true now, but wasn't true when those panels were installed. There were subsidies available to get the market kick-started.
They consist of an extra payment for every kwh you generate on top of the payment for delivering the power to the grid. The amount varied depending on when you signed up to the scheme, but at certain points it was as much as 50p/kwh (+ inflation, so more than that now).
There are incentives for high performance and efficiency. GPs are private partnerships contracted to treat patients. They can keep profits.
There's been attempts to do more private outsourcing (with the NHS still paying), but they tend to work out less efficient when you consider the whole system, because, for example they might only treat the easy cases and leave the hard ones to the normal hospitals.
It sounds like the organizations thing might just be to stop foreign nationals using that as a workaround.
Location: Oxford area, UK
Remote: Yes (happy with hybrid — 2–3 office visits/month to London, Reading, Bristol, Birmingham, or similar)
Willing to relocate: No
Technologies: TypeScript, JavaScript, Node.js, React, Python, PHP, PostgreSQL, MySQL, MongoDB, Docker, GitHub Actions, GitLab CI, broadcast automation (Sofie/Bitfocus Companion)
Résumé/CV: <https://arjam.net/cv.pdf> (see also <https://github.com/rjmunro>)
Email: [email protected]
About: Senior full-stack engineer, 25+ years. Recently shipped major Sofie TV studio automation features for the BBC and SVT (<https://github.com/Sofie-Automation/Sofie-TV-automation>); my contract is wrapping up and I'm looking for what's next.My recent work is TypeScript/React/Node on systems that have to work live-to-air—timers, playout orchestration, real-time state—not just CRUD behind a login. Example: re-architected Sofie timers to move clock calculations server-side, cutting client timer ticks from 60/s to 1/s.
I also build the tooling around the code: shared ESLint/Prettier presets across the Sofie ecosystem, jamies-git-tools <https://github.com/rjmunro/jamies-git-tools>. I have given company-wide Git talks and have wired up CI on GitHub Actions, GitLab CI, CircleCI, Jenkins, and others.
30 years of volunteer live A/V (sound engineering, directing, vision-mixing, streaming, camera operating, video editing).
Interested in broadcast/live media, live events, full-stack TypeScript, and developer tooling.
Google has been dealing with accounts opened for fraud, spam and other evil bots since their inception. They should be nuking those. What's needed is some way of reverifying an account that was closed incorrectly, maybe some kind of independent ombudsman service or something to get the account back.