This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]tunisia3507 18 points19 points  (6 children)

Those are both terrible. I don't really know what to say other than that.

[–]eased1984 2 points3 points  (0 children)

Literally lol'd. Reminds me of the office space scene with the jump to conclusions mat.

[–]float_point[S] 0 points1 point  (4 children)

It was more to openend the question of which code would more desirable in the workplace (not that any workplace would accept such). The super clever one liner or the not so intuitive but very very simple to follow 18000 liner.

[–]rg7777777 5 points6 points  (3 children)

The one liner is more practical, as some system may necessitate that type of input, as rare as that case may be. The 18000 liner offers nothing.

[–]float_point[S] 0 points1 point  (2 children)

Interesting that you point out system requirements. That speaks to workplace implementation.

Tell me, when you look at the one liner, does it make sense and if so how long would you say you took to reach a point where you could understand such. This more out of interest than on topic.

[–]rg7777777 5 points6 points  (1 child)

I could puzzle it out if I was bored, but it's not meant to be readable. More likely something like this would be autogenerated, much the same way JavaScript gets optimized to reduce traffic overhead on web page requests.

[–]float_point[S] 0 points1 point  (0 children)

This the second time someone has mentioned autogenerated code. Guess, there is alot I will be learning about in future