well, you said the exact same thing I have been thinking for a while. "clever" code looks cool and but is not very usable if you going to be building large complex systems with many people working on the code and some will also be new to the team and others leaving. Code SHOULD and MUST be readable first and foremost. In the old days when memory was an issue and you had to make your code very very tiny in order to fit on to the chips those days then code HAD to be clever, but things have changed now, clever code limits extensibility in views. Yes, if you really think about it, the less memory you occupy the better but if it will take you a whole month to change your code as opposed to just a day because of trying figuring out WHY something was done then I'd rather have a bit longer code in order to factor in comments, a few more variables, and functions. Anyway, beside my rambling, there is something people are missing here, "best practices"

nice, clean and readable

Very nice, tricky for a new guy to JS like me to understand but beautiful