2 ms·
I'm far too insecure to force my taste in code on others like that. Though I find the Ascetics code utterly unreadable (is that why I still don't grasp Lisp?),
by mcv 13y ago
I'm far too insecure to force my taste in code on others like that. Though I find the Ascetics code utterly unreadable (is that why I still don't grasp Lisp?), and the Purist's code ridiculously over-designed.
But still, if someone writes code like that and I'm not the one reviewing it, my instinct is to assume there's a good reason for it to look like that. If I'm reviewing it, you can bet I'll want them to explain why they do it like that, and more importantly: explain what's so wrong about the original code that it needed to be changed.
- pavelludiq 13y agois that why I still don't grasp Lisp? I don't know what your history is with trying to grasp Lisp is, but if you write code like that, It's bad in pretty much any language. Code is to be read by people. Here is a lisp version of the first snippet in the blog post: (defun formatted-zip-code (digits) (case (length digits) (4 (format nil "0~A" digits)) (3 (format nil "00~A" digits)) (otherwise digits))) The syntax is a bit different from Ruby, but there isn't a single concept here a programmer doesn't know. My theory about why such cryptic code gets associated with lisp is because too many people were told they can learn something profound about programming by just jerking around with scheme without actually using it. So a lot of people just play around with abstractions without actually trying to build anything. That might be useful as much as any abstract task is useful(does solving sudoku puzzles make you a better programmer?), but not as useful as these people think. IOW it's just code masturbation. Lispers who actually write useful software avoid such code as much as anybody else, they'll be maintaining it after all :)