Teaching the Elephant to Fly
summary
Ford spends five to six years and an 11 billion investment to build Mustang Mach‑E as proof that legacy auto can ship software-driven EVs with unified UX and a 3.5s 0–60. The stack uses Autonomic/TMC plumbing, cloud partnerships (recent Google deal), and exposes connected-vehicle functions as APIs (location, command-and-control, vehicle status). Testing and CI use Postman+Newman+Jenkins with collections and runners. Analyst math on 75 million vehicles implies billions in subscription revenue if uptake matches assumptions.
AI-written summary · about
chapters (13)
- 0:00Introduction and welcome
- 1:30Talk overview and agenda
- 2:36The flying elephant metaphor
- 4:21Culture as the foundation
- 6:03Team Edison and EV program
- 7:09Ford Labs and software evolution
- 9:39Connectivity platform and TMC
- 12:05Mustang Mach-E features
- 13:07API-driven mobility ecosystem
- 15:15Postman as silent partner
- 20:28Ford-Google partnership
- 22:55Mustang Mach-E vs Tesla
- 24:24Q&A session
related talks
29mAPI-fying the Engine: Replacing Legacy Automotive Protocols with REST and OAuth.
15mAutomotive Grade APIs – designing for longevity
12mDriving technical excellence from the top: A case study in uplevelling
16mScaling APIs Globally: VW Financial Services's Revolutionary Approach
50mThe API Product Management journey: a simulation
29m10 years of OpenAPI in the Car Industry
21mAPI Evolution: Master the Future of Business Integration
42mBuilding Platforms for Developers