3 ms·
Build something cool. Rinse. Repeat. Doing exercises and plowing through books is great but solving your own problems, to me, is key. Most books won't even to
by whalliburton 18y ago
Build something cool. Rinse. Repeat.
Doing exercises and plowing through books is great but solving your own problems, to me, is key.
Most books won't even touch the surface of the real things you'll deal with, like how to interface to C or Java for example, or even mention the most important part of developing : other people's code.
My advise FWIW:
First set up sbcl/emacs/slime. This is really not debatable.
Then in no particular order - think holographic distribution:
a. Hang out on #lisp
b. Read comp.lang.lisp
c. Collect and read and use the free (as in liberty) libraries: http://cliki.net http://cliki.net http://www.cl-user.net http://www.cl-user.net
d. Build software for yourself and your friends
- lst 18y ago| b. Read comp.lang.lisp For laughing or for crying? There's not much in-between...
- whalliburton 18y agoFalse. There's gold in them thar hills! http://xach.livejournal.com/138588.html http://xach.livejournal.com/138588.html http://xach.livejournal.com/139017.html http://xach.livejournal.com/139017.html
- Hexstream 18y agoI wouldn't recommend hanging out on #lisp for a beginner. In my case it set me in a passive mode and I'd ask a flurry of questions that a little research in the HyperSpec and other appropriate reference documents would have answered.
- dmpayton 18y agoSee, I'm the opposite. I can be quite timid in IRC (though this generally applies to anyone I don't really know), and I always wait until I'm completely stuck to ask a question. Then I feel like a complete tool when someone points me to a link I should have found on my own. So, I don't think I need to worry about entering passive mode. :)