LispForum

Serves me right for posting before reading -- I saw the same thing and posted a link in Books & Resources

As seen on reddit:

http://clqr.berlios.de/index.html

I argue that shared hosting is going to die out. If I'm right, that could be good news for Lisp-based web apps.

I'd be interested in getting feedback.

I suppose I should add that the beauty of this is that Redmine and Trac can recognise issue numbers in source code checkins. In Requirements there's a lot of talk about traceability -- that you should be able to justify any code or test with a requirement, use case or business rule. It sounds fine i...

At the moment we use it internally. Redmine (and I think most of what follows applies to Trac also) allows you to define custom fields for issue trackers. So for instance I have a Use Cases tracker with fields for the Primary Actor, Goal, Success Guarantees etc. Then I put the body of the use case i...

I've usually worked from Software Requirements by Karl Wiegers. He promotes a lot of commercial tools, but at work we're experimenting with using Redmine (a Trac-alike) to store and track all our requirements.

AKA the favicon

Learning it, essentially. I'm sick of reading articles about how it's awesome, will find me women and stitch up my socks etc etc. Instead I want to be in a position to nod knowingly, and stroke a deservedly-earned beard of wisdom. Also, I've expressed thoughts about writing the Last And Bestest Blog...

I've heard good things about the PeepCode stuff on git. They have a introductory screencast and an ebook about git internals. I've been meaning to pick them up.

I prefer the classic command-and-subcommand pattern of svn, mercurial et al; but git has too much momentum to be ignored at this stage.

I'm working through ANSI Common Lisp as my holiday project. What it has over PCL is exercises, but the two books have different coverage of what is a pretty ginormous language.

I've found this site useful as a reference when I've finished my own solutions to the exercises.