Bad UX is Not an Option: Intuitive Software by being a Better Developer
summary
Claim: developers must own UX by instrumenting code. Practical tool: Monolog in Laravel, logging controller actions, validation failures and context (request, user id, job id) so the team sees exact failures, quota hits and how often they happen. Example: add logs before/after DB writes, route validation errors to Slack with a fingers_crossed handler, add a processor to attach auth user. Result: production logs replace guesswork and user tests and produce counts that drive concrete UX fixes — start logging.
AI-written summary · about
chapters (10)
- 0:00Start
- 8:22The Airport Effect
- 11:55don't fire the UX guys... yet
- 14:49Logging
- 21:01Tweaking Monolog
- 22:05Special Handlers
- 24:07Processors
- 27:11Build Around Expectations
- 30:48Consistency & Simplicity
- 34:50Watch for edge cases
related talks
37mUX Design and Education for Effective Monitoring Tools
29mObservability for Developers: How to Get From Here to There
29mAre logs a software engineer's best friend? Yes - follow these best practices
53mLizard Optimization
31mObservability for Developers: How to Get There
38mLogging as a Painkiller
57mThings That Work So Well for Me I Can't Believe You're Not Using Them
53mObservable Web Applications