I know it's protected information, but I am curious which types of fraud these amounts are awarded for. There seems to be lot of unpunished public examples of securities fraud (MLMs, cryptocurrencies, legislators dumping or buying stocks at convenient times, etc).
I've noticed a related effect, where every problem discussed in a retro has a "process" solution, because the team's own processes are the only thing the team can fully control.
This can lead to both a constant churn in processes and a piling on of additional processes, which bog the team down with an explosion of on-call-like rolls that get rotated through team members.
One thing that we always did towards the beginning of a class was an exercise where we tell them to write down the steps to make a peanut butter and jelly sandwich. Then we'd literally get bread, peanut butter, and jelly, and follow their instructions to the letter. No one ever adequately describes the process: "put peanut butter on bread" - With what? the jar is closed, I can't! etc.
You might argue this introduces too imperative a thought process - but it gets the "computers do exactly what you tell them to" idea across very well.
I had a music teacher do exactly this to a class when I was 10 or so, and it's one of the most memorable school experiences for me as a child. The purpose was something like explaining yourself well, rather than programming, but the idea is the same.
We needed to describe how to draw some sheet music on the chalkboard, but you couldn't gesture (we could only communicate through an imaginary phone line), and he would take whatever you said as literally as possible and opposite of your original intention as he could.
"Ok, draw 5 lines" (Draws 5 squiggles) "No! 5 straight lines" (draws 5 lines in various locations and directions) "Nooo! 5 straight lines, above each other, horizontal!" (Draws the 5 lines of a musical staff, but 2 inches long and 3 feet vertical spacing between each line). "Nooooo! 5 straight lines, above each other, horizontal, they should be very long and close together" (Takes out a piece of paper from his desk, draws the staff on it) "NOOOO! On the chalkboard!" etc
I think this is much more relevant to both coding, and applicable to other disciplines as well. I do very little coding, I don't find it interesting, it's not at all the same basic knowledge base as history, civics, math, science. Coding is a higher level that requires a base first. I'm not skeptical of introducing code at such a young age, but I'm skeptical of treating it as if it's a basic thing many/most/all kids should understand.
Since I didn't see this elsewhere - client certs have privacy concerns, because by the time you've done your handshake the other side knows exactly who you are. This pretty much rules out always-presented certs. Because of that, you would need to manage the certs more directly, and then you get into all of the UX issues around managing certs.
I think the McDonalds of the future may look more like a vending machine than a restaurant. Of the the things you listed, only "test a burger patty for the correct internal temperature" is actually related to producing McDonalds food, and that is certainly automatable.
But that aside, if all that's left is basic cleaning then McDonalds could simply contract a cleaning service. I'd guess that a single team could service at least 10 fast food restaurants a day. And then how many years before running the cleaning service only requires one person?
Might take some work to figure out how to run this on modern hardware, but I found it on myabandonware[0] if anyone's interested. They do have a guide[1] for how to play it.
I also just discovered there was a clip from it in recently-released and HN-discussed The Witness!
> You’re unlikely to see +1-DDoS-type behavior inside private repos, for example.
Maybe not, but the lack of an "Approval" system is keeping us from moving from Bitbucket to Github. The proposed fix for +1 spamming could easily serve as an approval system for us.
(Bitbucket, I might add, has also become incredibly stagnant, as can be seen by this long standing issue to support Markdown[0])
Where I live there is a minimum fare of $75 imposed on Uber cars leaving from the airport. I took an Uber there and had a great, simple experience ($34 fare) but had to take a taxi back when returning from my trip.
The cab was falling apart. One of the doors didn't open from the inside. The axles made horrible, periodic thunking sounds (I'd guess the CV joints but am no car expert). The engine light, the wheel stability light, and the SRS warning light lit up the dash. The cab driver drove 10-15mph over the speed limit and nearly side-swiped several other cars. I asked to pay with a card and was met with a grunt of disgust, even as I added a standard 10% tip.
I understand there are some regulation issues related to Uber in many cities, but given the experiences I've had, I can't wait to be rid of taxis.
I should add that in London I had the opposite experience, where the standard cabs (and official app) were fantastic, but Uber was price gouging during a tube strike.
As a Londoner I and most of my friends hate black cabs. The drivers hate going more than 2 miles out of the centre of town, the cabs spew out diesel and the fares at night are 4x uber.
The drivers have the knowledge admittedly but it is not enough. I give them 5 years. Max.
Life Hack: Put the "pin" in the Uber app, near the airport (where there is no fee). As soon as you get a driver, call and let them know you're at the airport, which terminal/exit you're at.
This avoids any fees, and also gets around the "We do not service this area" blockers.
Depends on the airport. Some airports are vicious about enforcing Uber bans (and the drivers quickly figure this out), so drivers will call to confirm your location if the pin is near the airport.
On the other hand, most airports have some sort of public transportation heading in a not-airport direction...
