Writing effective code comments

Good Programming Practices

- Writing effective code comments

First we need understand who will read my comments and why we write comments.

Who will read the comments?
This can make us know what we need write in the comments.
For developers who maintain our code, including ourselves.
For developers who will be interested in our project, want to use our project, call the exposed API.
One thing to remember is that they might be reading only the generated documentation without access to the source code.

Why we write comments?
There are already many arguments why we need comment, here I only want to say why we want to take time and efforts to write comment, and what we can benefit from it?

For our own sake, writing comments is a good habit that forces us to think and record why we write the code in this way.
It is also a good habit that forces us to plan and proof-read our own work.
Comments should be written before the code itself.
This can help us to understand what this class/method does, and whether/why it is needed.
This can force us to think deeper and improve our solution before really write code. A poorly conceived function will become more apparent when we try to explain our thinking in the comments.
This can also help use to save our time and effort.
If we write code in a hurry and later find it doesn't work or doesn't work as we wish, then we will have to rewrite it. It is always harder to find bugs and rewrite it and make sure our change doesn’t affect other component.

Comment is especially important for a project's successful, especially for an open source project.
If we want more users/developers use our project, extend it, or help us to maintain it, provide patch for it, good and complete documentation is essential.

Nobody would like to use the project if they have to strive hard to understand how to call the API, how to use it. Nobody would help us to maintain it, if he can't quickly understand the project source code.

How to write effective comments?
The most effective way is to choose more meaningful method/class name, which can explain itself.

Explain what a function does, not how it is implemented.
Explain why the function exists.
Document all checked and unchecked exception.
l          Document precisely the conditions under which each one is thrown using the Javadoc @throws tag.
Document parameter conditions, such as whether it can be null etc.
Document Requirements (pre-conditions)
l          What inputs do we need, and what state must the object be in, for this method to work?
Document Promises (post-conditions)
l          What state is the object in, and what values are returned, on successful completion of this method?
Document the invariants
l          Invariants are used to check that some condition holds during the execution of this method.
Document thread-safety.
Why this method is synchronized, and why not?
What this element can do, and what can't.
What should a user avoid doing with the API element?
How does this differ from any similarly named API elements?

Rules for Effective API Documentation
Document all API elements
Avoid un-documentation - say more than just the obvious
Don't postpone.
It's best to write comments first before delving into code, and never check-in undocumented code.
Write to the reader, not yourself.
Be concise
Use code examples when appropriate
Use cross-linking extensively
Be professional
Write complete and grammatically correct sentences that end with a period.
Use correct spelling and capitalization.

Writing Code Comments for Effective API Reference Documentation
Writing effective code comments

No comments:


Java (161) Lucene-Solr (112) Interview (64) All (58) J2SE (53) Algorithm (45) Soft Skills (39) Eclipse (33) Code Example (31) JavaScript (23) Linux (22) Spring (22) Tools (22) Windows (22) Web Development (20) Nutch2 (18) Bugs (17) Debug (16) Defects (14) Text Mining (14) Troubleshooting (14) J2EE (13) Network (13) Tips (12) PowerShell (11) Chrome (10) Problem Solving (10) Design (9) How to (9) Learning code (9) Performance (9) Security (9) UIMA (9) html (9) Http Client (8) Maven (8) bat (8) blogger (8) Big Data (7) Database (7) Google (7) Guava (7) JSON (7) Shell (7) System Design (7) ANT (6) Coding Skills (6) Lesson Learned (6) Programmer Skills (6) Scala (6) css (6) Algorithm Series (5) Cache (5) Continuous Integration (5) IDE (5) adsense (5) xml (5) AIX (4) Become a Better You (4) Code Quality (4) Concurrency (4) GAE (4) Git (4) Good Programming Practices (4) Jackson (4) Life (4) Memory Usage (4) Miscs (4) OpenNLP (4) Project Managment (4) Review (4) Spark (4) Testing (4) ads (4) regular-expression (4) Android (3) Apache Spark (3) Distributed (3) Dynamic Languages (3) Eclipse RCP (3) English (3) Happy Hacking (3) IBM (3) J2SE Knowledge Series (3) JAX-RS (3) Jetty (3) Mac (3) Python (3) Restful Web Service (3) Script (3) regex (3) seo (3) .Net (2) Android Studio (2) Apache (2) Apache Procrun (2) Architecture (2) Batch (2) Bit Operation (2) Build (2) Building Scalable Web Sites (2) C# (2) C/C++ (2) CSV (2) Career (2) Cassandra (2) Fiddler (2) Google Drive (2) Gson (2) How to Interview (2) Html Parser (2) Http (2) Image Tools (2) JQuery (2) Jersey (2) LDAP (2) Logging (2) Software Issues (2) Storage (2) Text Search (2) xml parser (2) AOP (1) Application Design (1) AspectJ (1) Chrome DevTools (1) Cloud (1) Codility (1) Data Mining (1) Data Structure (1) ExceptionUtils (1) Exif (1) Feature Request (1) FindBugs (1) Firefox (1) Greasemonkey (1) HTML5 (1) Httpd (1) I18N (1) IBM Java Thread Dump Analyzer (1) Invest (1) JDK Source Code (1) JDK8 (1) JMX (1) Lazy Developer (1) Machine Learning (1) Mobile (1) My Plan for 2010 (1) Netbeans (1) Notes (1) Operating System (1) Perl (1) Problems (1) Product Architecture (1) Programming Life (1) Quality (1) Redhat (1) Redis (1) RxJava (1) Solutions logs (1) Team Management (1) Thread Dump Analyzer (1) Visualization (1) boilerpipe (1) htm (1) ongoing (1) procrun (1) rss (1)

Popular Posts