News for hackers. Stuff that matters.
Re:The Focus to Say No (2011) by bluGill on Monday February 01, 2021 @03:22PM (#25993317)
If the question should be in a document, then I respond by opening the documentation and checking to be sure the documentation is right, and then fixing it as needed. That done I tell them to read the documentation and let me know if anything is hard to understand so I can fix it.

When writing it is very easy to skip steps that are obvious. So when "asks too many questions about the obvious" can figure it out from the documentation I know the documentation is finally good enough for everybody - including the person who doesn't ask enough questions.

Re:The Focus to Say No (2011) by kodah on Monday February 01, 2021 @04:31PM (#25994255)
That's an interesting approach. Generally speaking, my organization doesn't maintain large document repositories because they go stale quickly and our products are too vast to document in such a way.

For some context on my reply:

- We maintain one design document per project. This document references everything from the application specifications to the automation that puts it in production.

- Most documentation is written in line with code. Finding documentation is about as complicated as finding the right repository.

This is also why peer review (in our org) isn't limited by level. Ideally we'd get feedback across the experience spectrum to make sure not only code but comments make sense to everyone.

Re:The Focus to Say No (2011) by bluGill on Monday February 01, 2021 @07:41PM (#25996140)
That is why step one is review the documentation. If documentation isn't reviewed regularly utility is useless. By using questions as opportunity to review it I can keep it useful.