You will have to pay for damage caused by your vehicle. Even if the car is driving itself. Autonomous cars won't be viable if the drivers aren't taking responsibility. There will probably be some kind of contact that you'll have to agree to when buying the car. Seems fair to me. If an autonomous car is ten times less likely to get in an accident than a human driver, then your cost for insurance would be way down and the insurance would pay for the accidents caused by the autonomous cars. Accidents caused by unpredictable circumstances as well as software bugs would be covered by insurance.
The first rule it should follow is the traffic law. It shouldn't be swerving into an occupied lane, and if the car in front of it isn't autonomous (your drunk driver car) then it should slow until it has adequate headway to stop without a collision.
1) It's not really for the sake of being "Green". I don't consider longer battery life on my phone to be a "green" attribute.
2) Digital calulations are already estimations (try storing 1/3 in a float). There really is a tolerable threshold, and it does vary by the application. Software engineers already need to understand, and accept this uncertainty. If you could hint to the compiler that you were interested in this Lat Lon coordinate to 8 decimal places, but you weren't interested in the intensity of this floating point image to more than 2 decimal places, then you could allow your processor to speed up, and be more efficient. Another way you could use a hint is that I don't care if 1% of these pixels are completely wrong.
I would like to go to a bar with friends without one of them suffering the fate of the designated driver.
On the other hand, if you have a problem with drunk dialing, imagine if you had a car that could drive you to your ex's house with a voice command...
Even better, or also, you could host a stack exchange like service too, that people can record and exchange information for the projects they do during the semester. Teaching is the best way to learn, after all...
1) You can fill your resume with applicable experience, and be able to answer the question "What were you doing the last six months?"
2) Meeting and working with other software engineers can make a big difference in finding a good job. It's not what you know, it's who you know (and what they think of you).
For example, in that two seconds where it thinks there might be a problem, it could increase the gain on the brakes, and reduce the gain on acceleration. So if you are accelerating towards a stopping vehicle, it will not accelerate as fast, and if you start to brake, it could brake harder. Alternatively, there could be subtle gains to be had as well. In a hybrid vehicle, it might prepare to regenerate the batteries, or if you are in cruise control it could change the speed. There are a lot of complicated things happening under the hood of a modern automobile, and you'd be surprised how little it could take in a lot of cases to reduce fatalities.