Will We Have Self-Driving Cars by 2030?
A one-week seminar that begins as a technology forecast and turns into something harder. General Motors promised self-driving cars by 1976; seventy years of confident predictions have followed. Students work through what autonomy actually requires, then hit the questions the engineering can't settle — how safe a machine has to be before we accept it, who gets sued when nobody was driving, and why we forgive human error more readily than we forgive a computer's.
Open the student page for this topicOne-Week Instructional Plan
The Year 1 rhythm, with this topic's own twist on Monday's readings: students choose one article from each of two groups rather than reading everything, and bring a quote from each into Tuesday's breakouts. The deck splits cleanly into what the technology can do and what we are willing to accept — Monday and Tuesday respectively.
What the Machine Has to Learn
Free write (5 min): a rideshare arrives and there's no driver in it. Do you get in? The concrete version of the question gets far better writing than "how do you feel about autonomous vehicles."
Data work. The deck's opening half is history and mechanism:
- The 1956 GM Motorama film — "Key to the Future," predicting self-driving cars by 1976. Ask what it got right and what it got wrong. The deck intends it as a window into 1950s technology and 1950s culture, and students usually find it funny.
- The timeline, 1956–2019 — cable-guided cars in the 1960s, the DARPA challenges, Google starting quietly in 2009, Nevada licensing the first self-driven car in 2012, the first fatality in 2016, the first pedestrian fatality in 2018. Then ask for their own prediction.
- The levels of automation — have students identify the level of the cars they actually ride in, and find the level at which a driver is no longer needed.
- The machine-learning slides. Machine learning suits "simple and repetitive tasks at large scale." Then the list of what human drivers do without thinking: read the scene, infer why another driver is doing something, handle the exception (red light, but a police officer waving you through), and communicate with a pedestrian. Very little of that is simple or repetitive.
- The Turing test — could there be one for driving, and what would it look like? Turing's biography is a worthwhile short detour; he was persecuted for being gay, and the deck flags this deliberately.
Assign the readings — one from each group, with a quote pulled from each for Tuesday:
- Group A — 5 Big Challenges That Self-Driving Cars Still Have to Overcome (Vox) or No, You Won't Get Self-Driving Cars Anytime Soon (Verdict)
- Group B — Where the Billions Spent on Autonomous Vehicles by US and Chinese Giants Is Heading (CNBC) or How Driverless Cars Will Change Our World (BBC Future)
Quotes, Then the Questions Engineering Can't Answer
Mindful moment (5 min): Monday was the case for autonomy. What are the drawbacks and worries?
Breakouts (10 min): each student says which article they read, shares their quote, and explains why it stood out. Short, structured, and it gets every voice in the room before the formal seminar.
Then the four hard slides, in this order — they escalate:
- How safe is safe enough? The deck asks it brutally: how many American deaths per day would you accept in exchange for the benefits — 1, 10, 50, 100? Then the comparison: more than 100 Americans already die on the roads every day, about 90% of crashes are caused by human error, and nearly 60% of drivers in fatal crashes are intoxicated.
- The fatality-rate graph. Which line actually measures whether cars have gotten safer? (See the facilitation notes — this one has a right answer.)
- The ethical scenario. A mother with a stroller steps out; the car can swerve onto a sidewalk where two adults are talking, or stay its course. What's the ethical choice — and will we accept a computer making it?
- The liability scenario. A truck crosses the centre line and kills a self-driving car's passenger, in circumstances where no human driver could have avoided it. Who does the family sue?
Then the data problem: today's partly-automated cars generate about 25 gigabytes per hour, and a full sensor suite would produce roughly 43 gigabits per second. Set that against the storage-capacity chart, which has a logarithmic y-axis and a curve that has been flattening since the 1990s.
Open the Discussion
Mindful moment (5 min), then breakouts using the point-and-question each student prepared Tuesday. The core questions:
- How do you feel about self-driving cars — would you use one, or would you rather drive?
- Will we have them by 2030?
- Will there come a day when cars requiring drivers no longer exist?
- How much should we worry about hackers? A European cybersecurity agency report found autonomous vehicles vulnerable precisely because of the computing power inside them.
Before students leave: themes and lingering questions in the notebook, and each student posts one resource to the sharing board so classmates can read them before Thursday.
Student-Sourced Evidence
Mindful moment (5 min) — this one is personal: what have you driven, how old do you have to be for a permit where you live, and are you excited or frightened to learn?
Then students share resources, and each picks one classmate's link to read carefully and evaluate: why this one, and what does it add to what the week already covered? The deck's closing question is the one to end on — will machines ever be as good as us at some things, or will they eventually be better at everything?
Score Your Participation
The four reflective questions, then the participation matrix. Students also use the participation rubric to score the week and explain the score.
Notes for the Guide
The deck's own summary is worth keeping in mind all week: the technical challenges are immense, but the legal, ethical, and behavioural ones are bigger — and more interesting to argue about.
The Fatality Graph Has a Right Answer
- Deaths per billion vehicle miles travelled is the correct measure of whether cars have gotten safer. Raw deaths ignore population growth; deaths per million people ignore how much further people drive now.
- Deaths per million people is the right line for a different question — an American's personal risk. That fell from roughly 260 a year before the 1970s oil crisis to about 110 by 2017, a drop of nearly 60%.
- Total deaths and deaths-per-million diverge because the US population grew. If deaths held at 40,000 while the per-million rate halved, the population must have doubled.
- The killer comparison: the current rate is about 10 deaths per billion miles — one death every 100 million miles. Waymo's "20 million miles with no fatality" suddenly looks unremarkable.
Have the Data Answers Ready
- The sensor arithmetic: 6 radar at 15 Mb/s = 90; 5 lidar at 100 Mb/s = 500; 12 cameras at 3,500 Mb/s = 42,000. Total ≈ 42,590 Mb/s ≈ 43 gigabits per second. A 500 GB drive fills in under 12 seconds.
- The storage chart's y-axis is logarithmic, doubling at each mark — Moore's Law. Students almost always read it as linear.
- Growth was fastest in the early 1990s, where the line is steepest, and has flattened since. That flattening is the point: the data problem is growing faster than the storage solution.
Where Discussion Tends to Go
- The double standard is the week's real subject. Students will accept 100 human deaths a day and reject one machine death. Ask them to defend the asymmetry rather than mocking it — there are real arguments for it (consent, accountability, agency).
- The trolley problem eats the room if you let it. Give it a firm ten minutes; the liability question that follows is more tractable and less familiar.
- Phoenix is local. Driverless rideshares already operate there, and students may have ridden in one. Ask why Phoenix was chosen — wide roads, a grid, and almost no snow.
Adapting This Topic
- Optional extensions for students who want more: Why Don't We Have Self-Driving Cars Yet? (CNBC, video), Cars That Are Almost Self-Driving (US News), and Experts Warn There's No Easy Answer to How Safe They Should Be (BBC).
- Short week: merge Wednesday and Thursday and drop the find-a-resource step. Do not cut Tuesday — it carries all four of the ethical slides.
- Cross-curricular: the source notebook connects this to Science (remote sensing — lidar and radar) and Math (computer science and AI). It is a natural fit alongside a computer-science unit.
- Pairs well with: the robots-and-jobs topic, which takes the same automation question into the labour market.