Design and Reality
summary
An oil‑rig monitoring system logs alarms as if incidents end when the alarm is silenced, so engineers invent an alert condition concept that decouples domain state from noisy UI alarms, fixes logs, and models concurrent incidents; a copyright‑claims startup replaces tangled matching code with a temporal event‑sourced model and a trust value object plus polymorphic strategy objects to update trust, cutting hundreds of if‑statements, improving predictability, and making domain rules testable and configurable.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker setup
- 1:28Linear design fallacy in software
- 2:52Domain language vs ubiquitous language
- 6:00Oil rig sensor incident story
- 16:06Alert condition model discovery
- 25:56Copyright claims startup case study
- 39:06Trust as a domain concept
- 51:00Evaluating and refining models
- 53:27Conclusion and takeaways
related talks
47mVariable Monitoring with Declarative Interfaces
30mContext is All You Need: The Art and Science of Information Design
20mMicrointeractions for the System: Design in the Age of Techlash
03m"A Story about Design and Experience"
12mTrust, Design, and the Reality of Security Engineering in an AI-Driven World
26mAuraCast: A Multisensory Proof-of-Concept to Combat Alert Fatigue in Cybersecurity
36mDesigning Calm Technology
13m404 Fire Alarm Not Found