4 ms·
If we get better search systems I would be totally on board. But most knowledge base systems have a hard time finding similes for words let alone sorting articl
by Guvante 6y ago
If we get better search systems I would be totally on board. But most knowledge base systems have a hard time finding similes for words let alone sorting articles containing multiple keywords in a useful order.
Having the information written down is important if nothing else than a source of reasoning going forward (people tend to remember do X but rarely why in my experience). However saying that asking a coworker is a bad thing is giving way too much credit to the documentation.
Additionally if you are talking about anything but the most basic associations talking with people is a good thing anyway as you can discuss your idea and see if there are problems the documentation couldn't tell you about because said problem would be listed in a different place.
- y2bd 6y agoSure, I should make clear: documentation/wikis are best for who/what/when/where of things like - What permissions do I need to contribute code to this repo - Where are the telemetry tables for X event - Who’s the manager for project Y - When will my commit make it into production For the whys and hows that often warrant discussion, while I still think you should have basics documented (How do I add a new screen to this app, why do we call into this proxy service, etc) so that folks have a starting place, and then pursue actual discussion. Even if the wikis are literally just the most basic associations, I still believe that would clear up a ton of repeated and honestly unproductive discussion time.