slite VS clede

But that's also what makes it worse for large teams: the same "immediate" productivity doesn't always translate to clean long-time maintainable code. Working in a large teams involves creating the right incentives to developers for long term maintability. For instance, if developers have a hard time testing complex code, they're more likely to write unit tests to test components. In Lisp, testing complex code is super easy interactively, so unit-testing can sometimes be harder. (Actually, this was an inspiration for one of my open source tools: https://github.com/tdrhq/slite, I wanted to make testing as easy as interactive development)

For the FiveAM integration, there is also https://github.com/tdrhq/slite/

For instance, here's a custom tool I wrote that I can't live without today: https://github.com/tdrhq/slite/ (although I think somebody has since written a similar tool for LispWorks)

Also take a look at https://github.com/tdrhq/slite for a more natural TDD flow when running tests.

Here's the link to the project: https://gitlab.com/sasanidas/clede

There was a talk at the EmacsConf last year about CLEDE.

There is CLEDE which is going to be talked about at this year's EmacsConf.