4 ms·
If you have sound documentation and design methodologies, then even if someone leaves, you should be in good share. Whether that's going to be the case is anot
by joe_the_user 16y ago
If you have sound documentation and design methodologies, then even if someone leaves, you should be in good share.
Whether that's going to be the case is another question, of course.
- aycangulez 16y agoDocumentation cannot really replace first-hand experience with code. That said, code without good documentation can puzzle even those who wrote it in the first place.
- Scriptor 16y agoThe same could be sade for outside code, it just needs to be documented properly and be well-designed.
- joe_the_user 16y agoIdeally the code produced by an organization with coding standards should be more accessible than good written to different standards. Whether that happens, of course, is another question.
- rapind 16y agoThis might be true in some rare cases, but in general I disagree with it. The people who originally designed it, no matter how well documented, are much more likely to understand and be able to extend it. Tests help too, however losing your initial developers, if they were any good, will always have a high cost associated to it. You can get by sure, but it has a high cost. I think the difference in comprehension in pretty large. I think there are a couple things which cause this difficulty: 1) I don't enjoy writing reams of documentation, and I bet most other developers don't either. 2) I don't enjoy reading reams of documentation before I can dig in, and again, I bet most other developers don't either.
- jsharpe 16y agoThis is why it's really important to do code reviews. Not just so that any egregious practices are eliminated before they are inflicted on the codebase, but also so that more than one person knows what's going on, and what the original intent was, with every piece of code in the codebase.