←back to thread

-2000 Lines of code (2004)

(www.folklore.org)
513 points xeonmc | 4 comments | | HN request time: 1.218s | source
1. kookamamie ◴[] No.44385043[source]
Lines of code is a byproduct, not the goal.

Code is an artifact, undesired debris.

The fewer lines, the better.

replies(2): >>44385144 #>>44385465 #
2. Koffiepoeder ◴[] No.44385144[source]
Well, like everything it's probably a balance to strike. Otherwise you may end up with highly golfed IOCCC-style code in production, which I would definitely not recommend.
3. _Algernon_ ◴[] No.44385465[source]
I've seen advent of code one-liners, and sometimes more lines is better than a one-liner.
replies(1): >>44385495 #
4. kookamamie ◴[] No.44385495[source]
Yes, my thinking here isn't about the semantics of code, whether it is written in dense or terse form, but about the more meta level - code itself is something we write to achieve some goal, it shouldn't be the goal by itself. As an example, as a company is audited for their valuation, it is not the code amount itself that is valuable. In many ways it can be seen as a burden, as you'll need to maintain code over time.