A fairly large and extensive commit affecting many lines can have a small impact on the absolute number of lines (which can even shrink). We change as well as delete existing lines, not only add new ones.
The lines which are replaced by new lines should be regarded as deleted lines, and so the figure of how many lines there are now should be supplemented with how many lines were deleted since the beginning of the project: how many additional lines of code exist in the repo's history, which no longer appear in the current baseline.
The invisible lines that disappeared in the history are the underpinning for the current lines; they enabled the new lines to be figured out, which took work. Someone had to write each line, and it has to be counted in the LOC output.
It is not entirely clear cut. If you make a trivial change in some existing line, it's not the same thing as a brand new line. Yet, according to the line-based diff tools, it looks like a deletion and addition of an entire line. Minus this, plus that.
You can't really say that, though.
Let's roll back the clock to when the project was new and say, only 10k lines of code. Maybe that first 10k was written in a month. Fleshing things out, then adding features like crazy. Coding in a euphoric state.
Once you've reached a certain amount of code, you're doing maintenance. Fixing bugs. Re-factoring code. I can see 10 lines of code per day. I notice that in my own projects. I might write a few thousand lines in a week and then as time goes on, I write a few hundred, then a few tens, then maybe just a couple edits.
You must be fun to code with.
Good quote. Took me until my 30s before I started realizing this myself. Seems obvious in retrospect.
http://www.cs.utexas.edu/~EWD/transcriptions/EWD10xx/EWD1036...
...if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger.
2 December 1988
ok
> CVE-2013-4484: Varnish before 3.0.5 allows remote attackers to cause a denial of service (child-process crash and temporary caching outage) via a GET request with trailing whitespace characters and no URI.
:|
Maybe I'm a bit odd, but I got into programming with code golf, using lots of J, K, and others. So my growth has been the opposite. It was just last year that I realized it's okay (and maybe necessary?) for other people to read/understand my scripts.
It is definitely good if other people can read your code, so you use great name convention and maybe add comments here and there, but is definitely better if people don't have to read your code because your code simply doesn't exist.
If you can achieve the same result with a careful design, a lot of hours of thinking and very few hours of typing, supposing that the design and the code is understandable by your peers, your code will be "more valuable" that if you achieved the same result with a lot of code.
Code is a liability is not ab asset.
> Code is a liability is not ab asset.
That's a great quote. I guess there's a sweet spot. Maybe, if only a handful of people need to be able to understand what you wrote, then the sweet spot can be skewed toward the terse end of the spectrum.
Have you never found yourself in the position of not being able to read/understand your own code/scripts? (Though, I guess if it's so compact as K/J and very in-grained, I guess it might be possible to get the overview pretty quickly?)
Just FWIW, I'm in the position that other people definitely need to read/understand my code/scripts. After running git-blame I sometimes really hate past-me.
It's just so awkward. Yet the grammar isn't bad; there is nothing wrong with "walk slowly" or "eat slowly".
"Ponáhľaj sa pomaly" is perfectly euphonic to the Slovak ear, while "hurry slowly" seems clumsy somehow. We need to make it more sophisticated somehow, like "make slow haste", or "slow haste makes faster" or whatever.
What is the reason ...
I suppose; if everyone said "hurry slowly!" it might wear into usage.
https://www.cs.utexas.edu/~EWD/transcriptions/EWD10xx/EWD103...
Also, the varnish source is really nice! Pen kode ;)
http://programmers.stackexchange.com/questions/103807/what-i...
