4 ms·
Lisp is the only language where you spend more time thinking than writing code That may be true for some people, but it's definitely not true for me. I'd say
by cperciva 18y ago
Lisp is the only language where you spend more time thinking than writing code
That may be true for some people, but it's definitely not true for me. I'd say I spend on average 10 hours thinking for every 1 hour I spend writing code -- and I write in C.
- wheels 18y agoI think the commenter meant something different from the original author. I think they meant that you spend more time thinking about how to write it in Lisp. I'd contest both points, really. First, I think if you're sufficiently comfortable in almost any language, you can translate pretty fluidly from idea to implementation. There are real differences, but they're overstated. In that respect, Lisp's "hardness" is really not being deep into the language and natively breaking problems down in a way that maps to functional languages. Second, and I think your point, is that getting to that point where you've got the problem broken down into its components is the hard part. I think there are tasks where that's true and ones where it's not, and again, that's largely language independent, though the amount of time needed for the more menial aspects does vary.
- Zak 18y agoLisp's "hardness" is really not being deep into the language and natively breaking problems down in a way that maps to functional languages. I think that may be a valid argument if you're talking about a mostly-functional dialect of Lisp like Clojure. Common Lisp and Scheme don't really offer any resistance to writing in an imperative style
- parenthesis 18y agoI was going to say: but a project like tarsnap, by its nature, is going to have a particularly high ratio of ideas to loc. However, even in a language like C, whose basic building blocks are much simpler than those available in a Lisp, and even when writing a routine program with no fancy math or theory behind it — if one finds oneself having to write lots of loc per thought, then one is doing it wrong: and one stops and thinks, and works out a way to abstract out the drudgery with more sophisticated data structures and preprocessor macros, or whatever.
- jacquesm 18y agoThat is the way it should be, not the other way around. Solving problems is hard, solving them in the 'right' way is even harder. For every hour that you spend thinking about your code you are probably saving 10 hours on code that you'll end up tossing anyway or that will perform horribly and will need extensive rewriting or optimization. If there is one common mistake I am guilty of then it is to sit down and start coding too soon.