My advice to the company BOD & shareholders: have him take the Udacity's self driving car online course and after the first project, he'll clearly understand how limited detecting lanes by CV only can be. To Uber's ex-CEO's point: LIDAR is the SAUCE.
From https://www.tesla.com/autopilot: "All Tesla vehicles produced in our factory, including Model 3, have the hardware needed for full self-driving capability at a safety level substantially greater than that of a human driver"
Why do we keep referring to something that we understand should require human supervision as "auto"? Stop the marketing buzzfeed and let's be real.
The Odersky's course is phenomenal. Highly recommended and it shows how much attention and craftmanship was put into designing Scala. Bonus: Martin speaks like Arnold and it's very enjoyable to have a "Terminator" voice teaching you complicated material.
Interestingly, you took the same path I did with Scala and ML. My criticism about these courses is that some of the projects and content can be too easy to get right, skimming on the surface in some areas that would need more time to grok. Lately I've moved to Udacity and there I can find more in-depth projects and discussions with virtual classmates. The price is steep but you pay for what you are getting.
Swift feels very immature in many areas. For example, Swift fails with generics out of most ordinary cases. Today, you still can't restrict protocol conformance (inheritance clause) to a type-constrained extension. That's a big issue with arrays. A struct wrapper is the go-to solution for many things where Swift generics break down and it's not the best or more elegant way to resolve its limitations. Many hopes for Swift 3.0 but I doubt they'll fix those.
My advice to the company BOD & shareholders: have him take the Udacity's self driving car online course and after the first project, he'll clearly understand how limited detecting lanes by CV only can be. To Uber's ex-CEO's point: LIDAR is the SAUCE.