Comments are extremely important—especially in large companies where there are often high standards for code documentation. You can usually judge a programmer's skill level by looking at how they write comments. That's why it's crucial for developers to form the habit of writing good comments in their daily work. In many cases, the ratio of comments to code can be 1:1, or even 1:2 or 1:3.
I’ve experienced this firsthand. Sometimes when someone sends me code to modify, the source code is a complete mess—densely packed, no comments in sight. Modifying that kind of code is pure agony. I have to figure out what every variable means, what each statement does, what the purpose of each block is, and so on. Honestly, I’d rather write the feature from scratch than try to decipher that kind of code. So writing good comments doesn’t just benefit yourself—it can be incredibly helpful to others, too.
Well-written code must include clear comments. Reading thoroughly commented, well-structured code is a real pleasure—something only fellow programmers might truly appreciate.
Make writing comments a daily habit. There are two main reasons:
Other developers will use your code, so comments improve readability. If your code isn’t annotated, others might prefer to rewrite it from scratch rather than try to understand it. That’s inefficient.
You’ll need to read your own code later. Memory fades—there will come a time when you don’t remember what your own logic meant. Good comments help you quickly recall the original purpose and logic behind your code, saving time and effort.
Start now—add comments to your code. It will help you walk more steadily, and go much farther.
Visit the https://payhip.com/OracleeBookSoftwareShop website to get an e-book about Oracle internal storage.
Top comments (0)