Comment by MoreQARespect
1 day ago
This problem can be solved by making documentation a natural side effect of the actual work.
One way is by recording video calls where the decisions are made with transcriptions which can be interpreted by LLMs.
Another is generating docs from tests.
Yet another is making a rule that answers to code review questions must be turned into code comments.
There's also a huge amount of untapped potential for turning conversations in slack into documentation.
The issue with wikis, etc. is yea, that it isnt a side effect of the work itself. It is work, and thankless work at that.
All good points. It is perhaps a bit easier with software, where you can put comments and hyperlink directly in the code. It is a bit harder with a big, long-lived physical artefacts, such as a nuclear reactors.
The broader point was to make documentation a side effect of the work rather than a separate task. The opportunities to do this are not obvious but they are there.
I imagine this principle can probably be applied to nuclear power plants too but I dont really know how they work or what software they use so it's hard to come up with examples.