I actually agree totally, but perhaps not for your intended reason.
I have a hunch that the clear syntax and relative simplicity of web programming is what drives a certain kind of developer to long for complexity and turn something simple into this:
`user.public? && (current_user.try(:test) ? user.test? : !user.test?)`
Yeah, that's something that a developer learns better as he gains experience, but as a younger dev I know that I craved complexity for complexities sake, and to prove that I COULD work with complexity. I've since grown out of that.
I have a hunch that the clear syntax and relative simplicity of web programming is what drives a certain kind of developer to long for complexity and turn something simple into this: `user.public? && (current_user.try(:test) ? user.test? : !user.test?)`