3 ms·
This is the right answer, but in my experience, there's still a balance between wanting to be friendly, supportive, and engaged with the team, and wanting to pr
by sanderjd 11y ago
This is the right answer, but in my experience, there's still a balance between wanting to be friendly, supportive, and engaged with the team, and wanting to protect your own time. At its worst, the approach you outlined devolves to the "read the manual!" cultures that everyone hates, but if you can strike the right balance between writing documentation and helping people understand it, then you're in really good shape.
- LukeShu 11y agoI've found a pretty good balance to be giving answers that have 3 parts: 1. a short answer (about 1-2 sentences) 2. what section of what manual to read for fuller information 3. other resources; possible "gotcha"s Then, if they come back and still don't understand, don't just take the time to help them, but also update the manual with whatever you tell them!
- sanderjd 11y agoYeah, but this is a classic problem of long-term vs. short-term optimization. In the long term having great, living documentation of everything the experts know is clearly the best, but in the short term it looks very expensive.