Thinking in Lisp

SQL, Lisp, and Haskell are the only programming languages that I've seen where one spends more time thinking than typing.
That's because it takes forever to think of the solution in Lisp and Haskell as opposed to a decent language. Faggot lispers will spend most of their time figuring out how best to abuse recursion because they think it makes them leet programmers or some shit.

>>8
Not exactly, I sometimes spend more time thinking than writing code, but I end up spending much less time doing the sum of both than I would in another language. It's not like you don't have to think what your program has to do in another language, well, unless you got some ``architect'' doing all the thinking for you and he just tasks you to code some specific module, however regardless of that, someone has to do the thinking - in Lisp, you tend to do be able to just translate your thought more directly into code than in other languages.
>>9
Learn both. I mostly write Common Lisp these days because it lets you do a lot more things portably (across many implementations and OSes) than Scheme and overall has many features by default as well as lots of user libraries which just work with most implementations. Scheme is easy to learn either if you already know CL or if you're starting from scratch (although learning CL after Scheme might be harder for some if they dislike the Lisp-n style or other things CL does different from Scheme). Scheme has a small standard document that you can just read in an evening, although of course, if you actually want to understand what the language is all about, you should read SICP and the Lambda Papers.