English Deutsch Français Italiano Español Português 繁體中文 Bahasa Indonesia Tiếng Việt ภาษาไทย
All categories

computer programming

2007-09-07 05:48:03 · 4 answers · asked by Sanie 1 in Computers & Internet Programming & Design

4 answers

I use documentation because I write so much code that I can't always remember exactly what every piece is doing. It's also good so that other people can edit your code without coming to you for questions.

There is (almost) nothing worse than having to fix or edit someone's code that doesn't have documentation. If you don't do it, people will hate you. If you do... people will LOVE you.

2007-09-07 05:57:12 · answer #1 · answered by Albert L 3 · 0 0

If you intend your program to be used, then it's good to leave instructions on HOW to use it.

You may want to write instructions for even yourself. For example, if you go on vacation for a year, and you had written into the program, a special hidden feature that took a gesture with your left hand and holding the center wheel of the mouse while tapping your right toe precisely once per second, you might forget that during the one year!

More seriously, if you intend the program for someone ELSE to use, and you CARE that they'll be able to take some advantage of it and it'll gain them something in their efforts, then you should leave instructions. Don't assume they have the same mindset as you. Write clear, concise documentation! (And don't be like Microsoft and tell them to "See their System Administrator"!)

2007-09-07 05:58:41 · answer #2 · answered by fjpoblam 7 · 0 0

Comments within web code are helpful to all that read them. Many times you may write code and not look at it at all for a long period of time by then you don't know why you wrote it that way in the first place.

Most legal contracts that I have seen though so far for web design and development restrict the purchaser from being able to modify or hire another to modify your copyrighted source code. However if you are not writing it under a contract then anything you write becomes property of your employer to edit as he sees fit. In the later case comments or other documentation may become very valuable should your employer decide to replace you.

2007-09-07 08:20:50 · answer #3 · answered by Kevin 4 · 0 0

To give some other person who might look at your code a reason as to why you did what you did.

2007-09-07 05:53:27 · answer #4 · answered by blazeimurill 3 · 0 0

fedest.com, questions and answers