Given that the vehicles need to process an insane amount of data to effectively operate autonomously, it seems useful to allow them to send a snapshot of some of that data to the police if you push a "some driver is driving criminally around me" button.

The doctor is almost certainly weighing the risks here. If you really believe that his motivation involves fear of lawsuits from someone that can't get vaccinated, getting sick from a patient that is "voluntarily" unvaccinated, I submit that the risk of this happening is quite low, which implies that the doctor believes the risk for your nephew is even lower. This could come from, I don't know, many years of practical experience dealing with vaccinations of thousands of kids, many of whom are allergic to many of the components in a vaccine. I'm just guessing, though. Instead of second-guessing the doctor and assuming that he'd rather roll the dice with the life of your family, maybe you could just try talking to him so that you understand why he isn't as concerned as you believe he should be? You might learn something.

Sorry, but I question the accuracy of any quote that involves a doctor requiring that they knowingly inject a vaccine into someone known to be allergic to that vaccine. No doctor would ever require that their patients submit to being killed. So I have no reason to believe the rest of the story.

It seems quite likely to me that many parents make claims of allergies when they really just fear vaccines but don't want to tell their doctor that. Or, in this situation, maybe the doctor's office wasn't actually aware of the allergy, and the parents are tacking on a bit of hyperbole to their story.

No.

Why do you want to transfer the domain when you can just give him/her control of the web site? You can continue to own the services on the domain that matter to you (mail) and they'd own the HTTP service on the IP address you point the domain to. This could even be an intermediate step to full ownership transfer once you've moved your identity someplace else and are comfortable with the new owner of the domain taking more ownership over it.

There are technical solutions to these problems, such as tracking language/BIDI overrides when embedding strings provided by users (and reversing the effect afterward). You could also do it the "easy" way and just filter out characters based on their Unicode property (e.g. disallow all 'other' characters, which would include these formatting characters).

You say you've done some "basic" testing, but one of the biggest challenges for me upon entering a "real" software development role was adapting to test-driven development. Even if you don't take this all the way and write up all of your unit tests before you start coding, you do have to completely re-think how you structure your software so that it can be testable at all. This means breaking up your functions not just into parts that make it more readable, but into parts that can be independently tested. Usually this means breaking out your dependencies into interfaces, so that they can be mocked out (oh, and learning how to mock things), avoiding side effects, that sort of thing.

Also focus on writing readable code. I usually make one or two passes after I think I've gotten everything written and refactor with an eye toward making everything readable and understandable.

So you're saying that it is cost-effective (and perhaps a revenue source?) to lay conduit and fiber alongside every rail track in the US? Does this include existing rail lines?

It was always my experience that remote rail equipment was connected to public networks (PSTN mainly, but cellular and radio also). Are you saying that this is not true? Could you elaborate on the reasons that the railway systems discussed in this article were connected to a public network, since you seem to be saying that your lines have access to a private network?

...yet. You're assuming that autonomous vehicles will always resemble the vehicles Google is currently testing. I can easily imagine a future generation of autonomous vehicles where manual control is only used for emergencies, and it's expected that people might be sleeping during their trips and might not be able to respond in a sufficiently timely manner to requests for things like pulling over.

It probably makes sense to have something like "traffic ops" that works like air traffic control, and can direct autonomous vehicles around manually as needed, which might include "pull over at the designated spot" or "go directly to jail". Keep this role separate from the police (or anyone else on the ground) to curb abuse.

SPDY is layered on top of TCP... **TCP** suffers from head-of-line blocking and therefore so does SPDY.

You are mixing up your protocol layers. Head-of-line blocking of TCP segments is a wholly different thing than head-of-line blocking of HTTP responses.