3 ms·
At worst, the code is there. This is much better than a person leaving who did some stuff manually. Obviously additional documentation would be great, but code
by matwood 7y ago
At worst, the code is there. This is much better than a person leaving who did some stuff manually.
Obviously additional documentation would be great, but code itself is a minimal type of documentation.
- orbital-decay 7y agoYes, but the lack of reasoning behind the implementation means that the new person has to reverse engineer it (practically speaking). This isn't always bad, but in most cases it is. My point was that by simply automating the process you don't institutionalize the knowledge as much as you move at least part of the problem somewhere else. It heavily depends on the application, though. In my domain the implementation is rarely self-documenting, and most of the system's complexity is usually baked into the spec or the human part of the process. In some other domains the proportion is completely different.