It's because such research has no obvious initial use that the public must pay for it; no private enterprise will fund it, and often it will be useless knowledge, but occasionally someone will figure something out that unlocks a whole new understanding of the world.
I gotta ask, did you spend a week sucking your teeth after that, or did you hand it to them and say "hey, you're paying for expertise and we got it to you faster than we estimated"?
The correct way is the send the customer the almost-final version and wait for the bug report. This way you show how quickly you can tackle the problem but don't make the task look too easy.
Can confirm—I made a smart chess set like this years back by soldering Hall effect sensors and wires manually to a wood board for 64 squares. Every new soldered connection feels exponential—totally makes sense they didn’t do it this way.
I would’ve probably done 4 4x4 PCBs instead so a single damaged PCB could be swapped out.
The presumption was about mechanical instruments, from a simpler time. As computers expanded from being purely mechanical, it never got revised, which is why it is being revised now (three or four decades too late, I'll grant you, but legislation is a slow process.)
Except it was revised once already to point out that computers aren't reliable. And then a decade later, at the peak of the dot-com boom, that revision was reverted after a review by committee.
Photos of ballots are a criminal offence in the UK, which obviously is imperfect in an abusive relationship, but does help set a general norm that the vote is secret.
SEEKING WORK | Cambridge, UK | Cambridge/London/Remote
I'm a software engineer with two decades of commercial experience. I've helped startups get started and big companies keep going.
I've organised a couple of jobs through HN now; it's been a good way to find interesting projects, and my clients have been pleased with the work. One said: "Thank you! I've played with it a bit and it looks very impressive! Way better than what I imagined this project could be."
I've worked on a very wide variety of web-based projects, as well as React Native, Windows, and other platforms, so I will be able to hit the ground running on most projects. If you're doing something a bit esoteric, that could still suit me – I've done image analysis of microscope images, processing big data for satellite imagery, devised novel algorithms, written network protocols, hacked on FPGAs, basically a bit of everything.
I did a PhD in programming languages so I'm pretty good at picking them up. In the last 5 years I've done commercial projects in (at least):
Typescript/Javascript (React Native, browser, and Node.js), C#, Python, Java, Swift, Ruby and Golang.
As well as building things, I am also good at talking to people to help figure out what we should be building. I enjoy working with other developers and helping the team learn, but I am also happy to get my head down and build what you need. I'm happiest on fixed-term projects that I can complete on a schedule that suits both of us, and my clients have been very happy with this process too.
For the average web app, it feels like JWT introduces some complexity (and footguns like this) for no real benefit. I mean, you can avoid a session lookup from redis or something, but that's hardly an expensive part of a request. You can always optimise hot, non-session requests (e.g. private image serving can use signed URLs)
Also, you can't revoke sessions ns unless you have a revocation list, in which case, why not just have a session list?!
One advantage revocation lists have over session lists is that they can be distributed via a bloom filter. Assuming multiple services need to validate against some shared auth service, this can be a significant reduction in round trips.
It's publicly-funded venture capital for ideas.
reply