High level overview on how to design Common Lisp software

[vindarel]

I'd like to see more about designing Common Lisp software, especially large systems, and CLOS, particularly for what kinds of problems it's best used and protocol design.

(Paolo Amoroso, Mastodon)

We can sketch notes on this issue.

[vindarel]

important steps:

• style guide (google's etc)
• the boring organization of a .lisp file
• reading and reading code
  • Shinmera's, like Kandria https://github.com/Shirakumo/kandria/blob/master/grass.lisp
  • 40ants', like Ultralisp, reblocks, the Telegram bot
  • Screenshotbot-oss, user.lisp et all
  • Hunchentoot
• conditionalize on implementations and architecture: feature flags #+ and asdf extensions
• decomposition, creating components: from one package per file to more files for one package, many packages, more systems in the same .asd, extracting systems, see Shinmera's modularize.
• refer to good books