"Engineering to embrace change" Or "How clumsy engineering can lead to powerful research – Part II"
summary
Builds and tests a throw-away experimental app for simple.org (nurses recording blood pressure) to shrink feedback cycles from two months to two weeks by bringing real users into the office. Uses ClojureScript-based prototypes with live reload, an in‑app in‑memory DB, data generators and model time and context (overdue lists, local addresses) plus Wizard‑of‑Oz screens to exercise flows. Engineers pair with designers, focus on happy parts only, keep an isolated environment, staff a tiny three‑person experiments team, and accept zero code reuse when production follows.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:27What this talk is about
- 1:44Context
- 4:28Location
- 5:27Basic Flow
- 8:43Experiment Methods
- 10:20User Studies
- 11:54The Proposition
- 12:24The Spectrum
- 16:09My Recommendation
- 16:24Demo
- 23:26Models
- 24:55Things to take away
- 28:42Extreme programming
- 30:42Simplicity
- 32:41Team size
- 34:19Conclusion
related talks
01h 01mArchitecture Decisions: A Case Study -
24mAgile working in a slow-moving world
55mKeynote: Experimenting in a Sociotechnical System in Software Engineering
30mEngineering in Overdrive: How to Thrive When Tech Evolution Goes Full Gas
55mTransforming Enterprise Development With Clojure
15mLive Programming a Live Programming Environment: An Experience Report
29mLazy Engineering
39mImplementing Programmer Anarchy