2 ms·
Al these comment/no-comment articles are a little precious. You write code to be executed efficiently, but also to be understood (and modified) by other people
by jacknews 5y ago
Al these comment/no-comment articles are a little precious.
You write code to be executed efficiently, but also to be understood (and modified) by other people.
Of course your code should be so easy to understand that comments are superfluous. But whats the problem adding the odd hint anyway?
And code alone is static, like a bridge. All the design motivations and decisions are reified, but the design conversation itself is lost.
That conversation is often recorded in separate systems like github, UML, etc, but why not at least reference those systems in the code itself - until IDEs catch up and allow combined/multi-level code/comment/design/architecture/requirements browsing.
- Syonyk 5y ago> until IDEs catch up and allow combined/multi-level code/comment/design/architecture/requirements browsing. And you thought Eclipse was a memory hog now! "Oh, yeah. IDE's down, Jira is... broken, not really down, but not really responding either, looks like they used blocking calls for that integration. You could probably null route Jira in /etc/hosts..." "This is why we did it this way, because the more obvious methods failed in the following ways..." is certainly a good example of a use case for comments.