Probably the single best take-away from the article is to never stop learning. I also like the tip about keep networking and building relationships.

Totally useless of course -- but it was a weird discovery nonetheless.

1. The cameras only show while operating in reverse;

2. The warning entirely obscures 30-50% of the view in one or more cameras;

3. The warning tells you that there is dirt or debris on the camera.

So, you are warned, that your vision, via the cameras could be better -- by deliberately worsening the view.

Genius.

To Wit:

*Excellent, heart-warming tale of exploration and discovery. Using deft allegory, the authors have provided an insightful and intuitive explanation of one of Unix’s most venerable networking utilities. Even more stunning is that they were clearly working with a very early beta of the program, as their book first appeared in 1933, years (decades!) before the operating system and network infrastructure were finalized.*

https://diffendoofers.wordpress.com/2014/04/17/the-story-abo...

This seems the beginnings of a 'New Detroit'.

Add to that, the rapid expansion of automation -- both in white collar and blue collar settings -- and it isn't hard to see why few can take solace in an extended recovery and expansion.

[1] https://www.sca.isr.umich.edu/files/chicsh.pdf

Recommendation -- don't stall the glider at heights between 10 and 25 feet from the ground. Also, avoid barbed wire fences.

A quirky features of lawyers: can be unusually petty.

Quirky features of programmers: can be remarkably correct and still be very opaque.

Not bad when you consider we were driving to the hospital at the time, and the accident prevented us from reaching the hospital as well as preventing us from calling on an ambulance.

3 'assists' that the car gave us:

1. Crumple zone is bigger;

2. Battery made our vehicle heavier;

3. (speculatively), the 'crumple parts', crumpled more and costed more -- leading to less (none) bodily injury.