4 ms·
how stupid is to measure code in terms of lines? Make all that a library then you can claim: A static site generator in only 3 lines of Python Measuring line
by jitans 9y ago
how stupid is to measure code in terms of lines?
Make all that a library then you can claim:
A static site generator in only 3 lines of Python
Measuring lines of codes is completely wrong. See the Scala trend were people race to find the shortest way to express something generating hard to understand code.
1) Code has to be written to be maintenable.
2) Code has to be written to be read by your coworkers.
3) The bottleneck while coding is not the keyboard.
- deleted 9y ago[deleted]
- z3t4 9y agoUnless you have put effort into squeezing as much logic as possible into each line, the less code the easier it is to maintain. With more code, more stuff can go wrong. It's not just because we are bad at writing code, we have probability against us. If the bug average is 1 bug per 100 LOC then 100 LOC will have less bugs then 10k LOC. We also have physics against us, reading and comprehending 10k LOC of code will take much longer then reading 100 LOC. With that said I do agree with you that LOC don't say much about anything. It's a stupid metric. With higher level languages, a 100 LOC file might actually be millions LOC if you include all the libraries. Them being libraries means they are mostly decoupled, which makes things better, because coupling is the root of most complexity.
- jitans 9y agoThat's not the point. Trying to squeeze the code in less lines as much possible is not the way to go if you loose clarity. Python coders keep repeting the mantra "less line of code" but in the mean time they keep typing: self. self. self.