Documentation Nobody Reads and UX in the Internal Dev Kitchen
summary
Ruslan Cheremin explores how human cognitive limitations affect internal developer experience, arguing that code, tools and documentation should be designed for human brains rather than idealized machines. He links UX principles and human factors research (e.g., rule complexity, automation ironies) to practical developer problems like unreadable documentation and poor engineering communication, and cites specific writings such as The Pyramid Principle and several blog posts with recommendations and examples.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:12Why documentation matters
- 5:12Lack of feedback problem
- 9:36Instructions in complex systems
- 16:35Automation and human factor
- 22:33Tools to simplify tasks
- 27:26Role of examples in learning
- 33:20Documentation as a tool
- 36:31Hierarchy and layers
- 41:53Addressing different audiences
- 45:07Documentation chaos
- 46:10Anti-examples and error consequences
- 50:28Reading recommendations
- 52:13Q&A
related talks
36mUX designers /developers collaboration anti patterns
28mDesigning for Success: UX Principles for Internal Developer Platforms
01h 24mWriting Documentation - Practices and Theory
36mDX, UX, UI - Things You Didn’t Notice & How To Fix Them
41mIt’s easy to create good looking products, but what about useful ones
33mBeyond Buttons: Crafting Satisfying & Easily Marketable Products
49mDX, UX, UI: Things You Didn’t Notice & How To Fix Them
42mUX for developers... Say what?!
