osest.blogg.se - Automatic pseudocode writer

While all of these points are true, it would be a mistake to go to the other extreme and never write comments.

You are, on the other hand, guaranteed that the computer is doing exactly what your code is telling it to.

Your compiler doesn’t check your comments so there is no way to determine that comments are correct.

Writing and then maintaining comments is an expense.

A bad comment is worse than no comment at all. While it’s easy to measure the quantity of comments in a program, it’s hard to measure the quality, and the two are not necessarily correlated. While there are many resources to help programmers write better code-such as books and static analyzers-there are few for writing better comments. We find some programs harder to understand than others, and we look to comments to help us make sense of them. Compilers and interpreters ignore comments and find all syntactically correct programs equally easy to understand. Famed MIT professor Hal Abelson said: “Programs must be written for people to read and only incidentally for machines to execute.” While he may have purposely understated the importance of running code, he is spot on that programs have two very different audiences.