Keynote: Value Driven Development - Maximum Impact, Maximum Speed
summary
Argues for targeting two or three high‑value problems a year and delivering each as a 3–4 month project that saves ~$1M–$5M, using rapid envisioning (interactive PowerPoint prototypes), then validate at scale (billions of rows, petabytes) against real data flows. Recommends exploiting cheap hardware (terabytes of RAM, 64 cores), collection‑oriented/functional thinking, lightweight DSLs and loose coupling (REST/Atom, microservices with real dependency checks, Erlang/OTP patterns), and strong testing like QuickCheck found critical bugs in React and LevelDB.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:56Outline
- 5:26Process Driven Development
- 6:46Leadership Matters!
- 10:05Tangible Requirements
- 10:35Envisioning - Requirements Through Design
- 14:28Value Driven Development Identify a high valne bottleneck which it accelerated will make a large impact on the
- 18:43Fast Software
- 19:54Let the Hardware Do The Work!
- 22:02Ship Less Code!
- 22:52Use Less Objects and Less Code! Object Refactoring harder than Changing Data and
- 26:14Insurance Legacy + SOA + EAP
- 30:55HR System Bottleneck
- 32:58Product at Risk - Massive Data Migration
- 35:26Modernize Legacy Factory Automation Challenge
- 37:13Enabling Loose Coupling
- 38:16Service Architecture and Design
- 39:08Testing is still 30-50% of Development
- 42:55Collection Oriented Programming • Programs written with a functional style of map. filter
- 47:20Analyst and Expert Programming Models
related talks
01h 11mKeynote: Value Driven Development
01h 16mKeynote 3: The Zen of Programming
39mKeynote - The gordian knot
49mKeynote: Debug your thinking
42mKeynote track Methods: "Quality is a variable"
41mKeynote: Is the Developer Lifecycle Dead?
43mKeynote: Decision-making for Software Development Teams
49mKeynote