What on earth does it mean to build AI software?
summary
Defines building AI software as delegating decision-making to machines, shows a concrete agent-based framework (passive U1, active/proactive U2, autonomous with motivations), compares model-driven vs data-driven approaches, cites Newtonian physics as designed models and convolutional nets (Hinton 2012) as learned ones, warns about faulty validation (mugshot criminality dataset), and points to a practical Google Maps hybrid that combines explicit models with learned traffic prediction.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:33The developer's conundrum: what on earth does it mean to build Al software?
- 10:30How do we describe and build systems where decision-making is delegated to machines?
- 20:08When we delegate decision-making to machines we need a model of the world.
- 20:42Design the model
- 24:07Validate the model
- 25:49Applications are hybrids
- 27:01Did you successfully delegate decision-making to software?
related talks
03mInterview
59mThe evolution in AI thinking and products of the next decade
03mInterview
29mAgentic AI: What It Is and Why It Matters
11mAutomation of AI: Accelerating the AI Revolution
46mFullstack AI: The Building Blocks for Production Ready AI-Powered Software
36mArtificial Intelligence: The Future of Software
20mDecision Intelligence: The Next Phase in AI
