3,413 karma · joined May 10, 2013
This can be done purely in shell, no extra tools!
Using node seems like cheating; plus you have to call it explicitly, you know you really want to use this to prank your colleague who left their laptop unlocked.
Rest, Immobilization, Cold, Elevation
The article mentions a shift from ICE to RICE (which I’m aware of) and then another shift to PRICE, which I’m not aware of— anyone know what the P stands for?
This strategy clearly seems to have worked well in some cases (Scientology, Hoover’s FBI).
Maybe you need a big institution engaging in the strategy, to obfuscate and diffuse the responsibility & blame?
Sun-fed beef?
Maybe we need to use 1024-bit types?
The preceding sentence is a hilariously cynical zinger:
“Those who have seen my Twitter posts know that I believe the role of the data scientist in a scenario of insane management is not to provide real, honest consultation, but to launder these insane ideas as having some sort of basis in objective reality even if they don’t.”
[1] The Prose Edda was written in the early 13th century; the earliest recorded Viking raids on Britain are late 8th century; original Viking culture/beliefs must be even older.
Have you tried Rust? It’s nice in this regard; variables are immutable unless explicitly declared mutable.
In the story, the Romans have somehow stumbled upon the industrial revolution at the height of the republic, the consequences are fascinating. Very good read.
Or that’s one weak-ass trolley.
This is a terrible analogy. Here’s a better one: I’m holding a potluck. If you decide to come, you can eat all you want. If you take food from my event, you can’t hoard it, you must share it, even if you’ve “made it better” by changing it somehow after you left.
Don’t like my rules? OK, don’t come to my potluck.
Yes, the article is overly technical and detailed, but it captures very well the eureka moment of understanding Rust’s memory management. Some aspects are subtle yet profound.
I am always happy to take a little more pain at code-writing and compile-time in exchange for more safety guarantees at run time; Rust is great in this regard.
Maybe after I take that course I’ll agree with you. I don’t think that’s a great option for most.
Everywhere in the US, the law around Terry stops[1] applies. In fact every time the police “pull you over” on the road is a Terry stop.
In such a stop, mere “reasonable suspicion” is required for police to require you to identify yourself. You’re not required to present ID but you must tell them your name (you could lie, but that’s another crime). You can be arrested for refusing to identify yourself.
In order to determine if your are experiencing a Terry stop, ask the officer “Am I free to go?”, if the answer is no, ask “Why am I being detained?” and the officer should state his cause. If it’s not valid you won’t be able to fight it until after the encounter, possibly after you’ve already been arrested.
Egregious example: The infamous NYC “stop and frisk” policy[2] was essentially a massive Terry-stop program.
[1] https://en.wikipedia.org/wiki/Terry_stop
[2] https://en.wikipedia.org/wiki/Stop-and-frisk_in_New_York_Cit...
Create a system like https://news.ycombinator.com/item?id=31668814 for voting.
Voters remain anonymous yet can still verify their particular vote was counted correctly (and in fact that all votes are counted correctly)
You’d still want a paper trail.
Have you considered running (# of cpus) parallel scanners continuously? An inbound query “hops on” the the least-loaded scanner; at each article/chunk the scanner runs all the queries; each query “hops off” and returns after it has completed the cycle through the entire DB.
The guilty parties were literally casting votes for people they knew would not show up.
It’s an identity issue, much harder, and with its own set of controversies.