I always write terse code, not only because it reduces the number of lines (which is important to me) but also because: - You clearly state the atomicity, that

I always write terse code, not only because it reduces the number of lines (which is important to me) but also because: - You clearly state the atomicity, that this thing happening in 1 long line is specific thought, intent, desire - it shouldn't really be on multiple lines - its easier to remove/comment out intent (as it is always self contained), replace it, optionalize it and reuse it. - Scrolling the code is damaging to the focus. - Once you learned the specific methods used to create terse code seeing it repeated all over again you will become more proficient in reading the code all around. - Its way more fun. Its like poetry in programming - why would we all write dummy boring stories. Language is everything (obligatory babel 17 mention: https://en.wikipedia.org/wiki/Babel-17 https://en.wikipedia.org/wiki/Babel-17)