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
- Cognitive load is what mattersminds.md
- Everything I know about good system designseangoedecke.com
- How To Do Lessalexturek.com
- How I ship projects at big tech companiesseangoedecke.com
- AI is removing the middle class of software engineeringblog.florianherrengt.com
- A Bunch of Programming Advice I'd Give To Myself 15 Years Ago | Marcus' Blogmbuffett.com
- How to ask good questionsjvns.ca
- The Surprising Power of Documentationnews.ycombinator.com
- To get better at technical writing, lower your expectationsseangoedecke.com
- How I Find Problems to Solve as a Staff Engineerlalitm.com
- Thinking clearly about softwareseangoedecke.com
- AddyOsmani.com - 21 Lessons From 14 Years at Googleaddyosmani.com