3 ms·
It's the programming equivalent of the people who try to put as many complex word in a sentence as possible to look clever. I met some people who were trying t
by maeln 9y ago
It's the programming equivalent of the people who try to put as many complex word in a sentence as possible to look clever.
I met some people who were trying their best to make everything a oneliner because "shorter is better" or whatever reason they had at the time.
The real reason I always saw was that it was making the code "hacker-like" (and completly unreadable) and they could brag about how clever they were.
- yen223 9y agoOn the flip side, I met people who thought Python list comprehensions were "magic" and should be avoided at all costs
- falcolas 9y agoI've met people who have created entire programs out of nested list comprehensions; "they're faster than for loops!". I don't avoid them myself, but you would be hard pressed to convince me to nest them, or do anything that takes more than one line to express.
- whoopdedo 9y agoI think that's called Scheme.
- btschaegg 9y agoSame goes e.g. for Linq. I know of people who would prefer screen-filling methods of multiple nested loops with throwaway datastructures and various checks sprinkled on top to a simple three-liner Linq expression. Funnily enough, their argument always seems to be "it's easier to read this, since I'm accustomed to for (x;y;z) if (foo ||(bar && baz)) lorem = ipsum; as a pattern."
- dep_b 9y agoI can only imagine they got scared after seeing the SQL performance of Linq to SQL and all Linq to ORM based stuff after that.
- animal531 9y agoAgreed. But on the other hand I also find that writing code is the same as speaking normal language. We each have our preferences, vocabulary, diction, style etc. I also jumped on the Linq wagon, but cringe when I see for example a Swift etc. reducer. So as long as that person writes his page of code at a decent pace with limited/no bugs I won't hold it against him.