The Importance of Good UX
summary
Argues that concrete UX fixes beat abstract exhortations: teams move from an auto‑generated REST API on node and sprawling Jenkins pages to a rebuilt UI called ace that exposes only repo and branch to start a test run, surfaces partial logs and plain‑English error messages, and consolidates CI, work management and GitHub actions behind one button. Shows that trimming form fields and surfacing the right data measurably stops users from “hating” the tools.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:34Frontend JavaScript
- 1:04Backend Ops
- 1:19Bad User Experience
- 1:49Screenshots
- 2:04Jenkins
- 2:19Link
- 2:34Logs
- 2:49Main Data Point
- 3:04Not Good Enough
- 3:19New System
- 3:34User Experience
- 3:49CI
- 4:04Starting a new test run
- 4:19More options
- 4:34Partial logs
- 4:49Click one button
- 5:04Outro
related talks
25mIt's easy to create good looking products, but how about useful ones?
13mThe UX of UX - Behind the scenes of effectively designing in the open
24mYou're Doing UX Unconsciously, Now Let's Make it Conscious and Intentional
01h 01mDevOps ICU: Improving DevOps Results by (Correctly) Integrating UX
33mBeyond Buttons: Crafting Satisfying & Easily Marketable Products
41mIt’s easy to create good looking products, but what about useful ones
34mUnderstanding UX (and UI) – a practitioner's perspective
25mSize matters: Why some projects can't do UX well