Precision In Technical Discussions
While working with the same people in the same problem domain for a long time, it's extremely common for people to take shortcuts when describing usage of a technical system.
While working with the same people in the same problem domain for a long time, it's extremely common for people to take shortcuts when describing usage of a technical system. "When the user submits the form, it fails" "When the process runs out of memory and dies, it will automatically restart" "Oh yeah the app is slow right now" "This API is harder for a user to use correctly" There's a general idea of what these statements mean, and they communicate the right idea most of the time (otherwise they wouldn't be said!). But in more heated conversations or whenever we are debugging particularly t
saved by
related reading
- Cocktail party ideasdanluu.com
- Choose Boring Technologyboringtechnology.club
- Essays on programming I think about a lot | benkuhn.netbenkuhn.net
- Patterns in confusing explanationsjvns.ca
- Say precisely what you mean.index.how
- How To Write Quickly While Maintaining Epistemic Rigor — LessWronglesswrong.com
- To get better at technical writing, lower your expectationsseangoedecke.com
- neverjustneverjust.net
- Charlie Deets | Presenting design workcharliedeets.com
- Technical Knowledge cho PM — Kiến Thức Cơ Bản Product Managementvietnamcos.com
- Stop describing the UI when you show stakeholders your work.linkedin.com
- The Surprising Power of Documentationnews.ycombinator.com