There is a great term in software engineering; “Code smell”. In computer programming, a code smell is any characteristic in the source code of a program that possibly indicates a deeper problem.

A number of years ago, a retiring Special Forces commander was being interviewed for a television program and he was asked the following question: “Are you concerned that your troops are becoming too technologically dependent?”

My Dad would speak of mechanical sympathy; the idea that you needed to understand how a machine worked to operate it efficiently and to maximise its operational life. For driving, it was listening to the engine, not braking too hard, and using the gears appropriately.

In the last article What’s what in 2020 with AV, I indicated that there were two big players to watch; Waymo and Tesla. This article is about Waymo and their history and will lay the foundation for the next article.

The following are projects that are in progress or planned for SEQ. This will help set the scene for what SEQ will look like.

Last year I posted a series of articles about road authorities and their responsibilities in supporting autonomous vehicles followed by a breakdown of the SAE’s Levels of Autonomy and why we should just stop thinking like that. It is so 201x-ish.

The SAE Levels of Automation are arguably no longer fit-for-purpose. Following is a summary of why I believe SAE Levels of Automation need to be discarded and replaced.

The Levels of Autonomy from the SAE are the yardstick that is impacting the automotive industry and societal thinking largely driven by the popular media.

The Levels of Autonomy from the SAE are the yardstick that is impacting the automotive industry and societal thinking largely driven by the popular media.