Not sure how my article even made it onto HN but HN has been my home page for 16 years so I'm pretty stoked.
A quick note, Common Lisp tooling documentation exists in a LOT of places, but I could not find a single beginner friendly map of the full development stack, so had a long chat with various LLM's to spin one up. Regardless of your views on this approach to things I hope the article helps some people get a better mental model of what the pieces are and how they fit together. It's helped me wade through a lot of choices and debug a few things.
Awesome! I've been reading SICP and Land of Lisp, and wanted to get a good idea of the ecosystem but was overwhelmed by the documentation. Thanks for making it easier for us!
I noted in the intro which LLM's I had used to research and edit with. Mostly because I could not find a simple map of the tooling layers in common lisp in one place so I "synthesised" one of my own. The map is really what I was in search of and AI helped make it so, however the article has been revised and edited a zillion times by me and contains a lot of contributions from the r/lisp community and for some it still has "LLM voice" so I don't know maybe my "voice" has gone LLM too lol.
Anyway if there are any specific corrections or mistakes in the article that need attention I'm always happy to get feedback.
Not sure how my article even made it onto HN but HN has been my home page for 16 years so I'm pretty stoked.
A quick note, Common Lisp tooling documentation exists in a LOT of places, but I could not find a single beginner friendly map of the full development stack, so had a long chat with various LLM's to spin one up. Regardless of your views on this approach to things I hope the article helps some people get a better mental model of what the pieces are and how they fit together. It's helped me wade through a lot of choices and debug a few things.
Awesome! I've been reading SICP and Land of Lisp, and wanted to get a good idea of the ecosystem but was overwhelmed by the documentation. Thanks for making it easier for us!
There's also vend (https://github.com/fosskers/vend) for package management and per project isolation.
This reads like AI generated text, which it probably is.
I noted in the intro which LLM's I had used to research and edit with. Mostly because I could not find a simple map of the tooling layers in common lisp in one place so I "synthesised" one of my own. The map is really what I was in search of and AI helped make it so, however the article has been revised and edited a zillion times by me and contains a lot of contributions from the r/lisp community and for some it still has "LLM voice" so I don't know maybe my "voice" has gone LLM too lol.
Anyway if there are any specific corrections or mistakes in the article that need attention I'm always happy to get feedback.
> Opus 4.6, GPT 5.4, Gemini 3.1 were all used to help research and edit this article