documentation - Source Code and comments for prototype development -
I am involved in a prototype development. We can not say that this is completely prototype development. It is partly following the procedures defined within the organization. As far as customer related it is a prototype development.
Problem Documentation We do not have the time required and architectural design is not set to design and prepare detailed designs. Although I have created an architecture for the system and have created a simple document explaining the architecture and the main components. Because it is necessary to share between the members of the team and the new people who come in the projects. All other implementation details remain within the code. For example, we're using several image processing algorithms, which are not officially formulated as a document. Everything remains inside the code and the brain that created it. We can not be sure that any special resource is always available in the organization or can not always keep it for that particular task.
My question is, how extensive comments should be contained within the code. This code trash will appear, if it is overloaded with comments, but for some more time it is necessary to keep the source readable and maintain later it will become a product.
A good test for the weather requires a comment to pretend you did not write the code ( Or if you do not have anybody who does not write it which will be better) go through the code and see if it makes sense, whatever goes in front of the straight forward, it should be commented further.
This is really hard if you write the code yourself, but since your team takes some time so that your team reviews the code of others. It will also help in spreading knowledge about your code base, when you lose your resources, at least the team members have seen the code.
Although you have classified this code as a prototype, my guess is that you transition out of the prototype phase that you do not start throwing your existing code and start from scratch. Commenting and documentation should be sufficient to assist in this, so your current code is going to take and increase it.
The idea of the prototype code is a naive person. You have a code that is ready to produce and which is not a code.
Comments
Post a Comment