301 karma · joined May 15, 2016
Then there's things like the folate blocking antibody (https://pmc.ncbi.nlm.nih.gov/articles/PMC4783401/) which you can do a blood test for, but again not all people with autism have the antibody.
If anybody has any ideas I'd love to hear them.
- Money (the concept) is useful to society as a store of value, so you don't have to waste effort bartering for things.
- Adding on to that, credit is useful to society since it lets humanity even more efficiently allocate its good and labor (stored as money).
- Finally, stocks, insurance, and other financial instruments are additional advanced developments on top of credit, where groups of humans (companies) can take on even more risky endeavors supported by investors or insurers.
So my view is companies like Jane Street facilitate these complicated value transfers, to let (e.g.) a spaceship company draw on resources generated by growing crops, selling shoes, giving haircuts, etc via a convoluted path through stocks, ETFs, whatever.
In 2010 or so we tried to adopt Mercurial at the small company I worked at, but the support for Git was just so much better - even back then. Git's popularity meant that tooling, documentation, and general ease of finding people to ask questions was 100x easier with Git, so we switched. I'd imagine the same thing played out many times over.
A few FAANGs did and still use Mercurial, but they're on their own islands and don't really affect the wider tech ecosystem.
For my Kobo, I wrote a mod that lets me redirect Pocket API requests, and a small proxy server that translates Pocket API calls into Readeck calls.
So far it's working flawlessly and my Kobo is using its built in Pocket viewer for Readeck instead. I'm hoping to open source it soon so others can use it.
It took so long to move tapes around and read the sequentially (no random access!), and as the data corpus grew it got harder to have a practical backup, even though the data was still theoretically extant.
Even after visiting the Sun Station I didn't believe it and thought it was a narrative red herring....so the ending was a surprise to me. Somehow.
> The vast majority of people do not know what a Kubernetes is; 99% my skills and knowledge are completely unnecessary to be Good At Computers. Turn it off and on, click suspicious UI button, plug in cable, open Google – these are the only requirements of the job.
However, the bits about Tensorflow and nmap makes me lean a tad towards https://xkcd.com/2501/. I think it's hard to tell exactly where the line between Good and Bad At Computers is.
I can't speak to their digital bookstore but they integrate with Overdrive for library borrowing.
One day, we got a big box of makeup at the office - turns out their warehouse had gotten so fast that in the time it took us to cancel the order they had already picked & shipped it.
After that we put "TEST DO NOT SHIP TEST DO NOT SHIP" as the shipping name and "123 Fake St" as the address to try and avert this scenario, which seemed to work until we could modify the system to hide those orders from the warehouse entirely.
1. Send the astronauts home on Dragon
2. Certify Starliner for human flight if it can make it home safely (uncrewed)
If the capsule can make it down, it doesn't matter if there were people in it or not, right?
Or what about scenarios where the company doesn't have code access to a critical dependency? It's not so unusual either - using a non-OSS DB or cloud service would qualify.
I think a better version of the law should mirror right-to-repair efforts: service providers have to release an API spec and not block attempts to point the client code at the new server, analogous to improving the "repairability" of the software with third party components. Constraining this event to when the service shuts down should mitigate economic concerns for companies.
There will be some overhead, but it might be a wash considering calling over a FFI often involves similar overhead to marshall / unmarshall objects. And the simplicity gains would be massive.