> Even if you do get proficient at this, there is still the problem that reading CL is not enough - it's CL + custom macro/DSL systems per project. That is tru

> Even if you do get proficient at this, there is still the problem that reading CL is not enough - it's CL + custom macro/DSL systems per project. That is true and expected. Because if you "got" CL it means you start any larger application by writing a perfect language in which to write that application. But with power comes responsibility. And this is where a lot of Lisp projects fall short. It is much more difficult to make a mess in a poor language like Java where you can basically ctrl-c/ctrl-v your solution than it is in super powerful language like Lisp that gives you no guidance on how to structure your application. Especially if you also have intelligent people on the project. Because intelligent people can make even more complicated constructs with which to shoot their feet. I wish every CL project had one guy with a long beard that can bring wisdom on how to deal with an infinite power of Lisp.