4 ms·
When I write code, I want to solve a problem, not write a book--that's what documentation is for. Whenever I code in Java, I always feel the language ends up w
by floppydisk 15y ago
When I write code, I want to solve a problem, not write a book--that's what documentation is for.
Whenever I code in Java, I always feel the language ends up working against me. To get from point A --> point B, the end result usually consists of having traveled through points C and D as well as having written a corpus of code whose length might rival that of War and Peace -- when working on a major project. Writing similar code in other languages, my LOC clock in at a fraction of the Java code. Personally, I've found the less LOC I have to deal with, the easier project maintenance gets, but that could just be me.
- bozho 15y agoAnd I always prefer self-documenting code. Because no one bothers to write or update documentation
- floppydisk 15y agoI don't think the practice of self documenting code limits itself to Java. If I choose descriptive names for my files, functions, classes, variables, etc., I can still convey the meaning of individual blocks of code and the entire project regardless of language. Hopefully the people reading my code would be able to grok that a method called "openXMLConfigFile" exists to open the XML config file and all the code contained within does just that, hopefully.