Re:Systemd for Developers I (2011)
by VLM on Wednesday September 17, 2014 @01:09PM
(#8331072)
"I think that comments mean that source code itself is not readable enough"
Or that the author understands something about architecture. From an internal code base that I can't cut and paste, there's a nice discussion in comment form that paraphrasing is something like "you'd really like to implement an AVL tree here because we do lots of lookups and AVLs are faster than RBs at lookups, but actual performance testing on the test cluster shows that under our real world workload, the slightly better writing performance of the RB outweighs the slightly faster reads, or TLDR do not blindly change this to a AVL thinking you'll win, because you won't".
(Oh and obviously business logic. I find nothing inherently technologically wrong with the concept of say, floats for currency, perhaps in a hard sci fi novel, although as a business logic concept that is widely considered horrifically wrong, and there's nothing wrong with documenting business logic in comments although float currency is a ridiculous extreme example... how bout, and this GIGO filter forbids negative interest rates or something, which makes math sense and computer sense but from a business logic perspective might be quite icky)
I agree with you WRT comments for regex looking like line noise or programming 101 style syntax comments "x = 1 // this step sets the variable x to contain the integer number 1"
Or that the author understands something about architecture. From an internal code base that I can't cut and paste, there's a nice discussion in comment form that paraphrasing is something like "you'd really like to implement an AVL tree here because we do lots of lookups and AVLs are faster than RBs at lookups, but actual performance testing on the test cluster shows that under our real world workload, the slightly better writing performance of the RB outweighs the slightly faster reads, or TLDR do not blindly change this to a AVL thinking you'll win, because you won't".
(Oh and obviously business logic. I find nothing inherently technologically wrong with the concept of say, floats for currency, perhaps in a hard sci fi novel, although as a business logic concept that is widely considered horrifically wrong, and there's nothing wrong with documenting business logic in comments although float currency is a ridiculous extreme example... how bout, and this GIGO filter forbids negative interest rates or something, which makes math sense and computer sense but from a business logic perspective might be quite icky)
I agree with you WRT comments for regex looking like line noise or programming 101 style syntax comments "x = 1 // this step sets the variable x to contain the integer number 1"