I find it remarkable that the one troll that came into the thread trying to start a flame bait got debunked quickly, but in a rather friendly tone. That speaks for the community.
I would love to be in a position when I had to learn Lisp for my job. I struggle to learn it because I never find a good use case for it at work or in fun projects.
I had to learn AutoLisp for my job. It wasn't really all that fun because I didn't have to do anything particularly fancy, just a bunch of 8th grade geometry problems over and over and over and....
Mostly, it made me very familiar with why one might want to find the intersection points of two circles.
Some of the things he misses have existed in some environments, but haven't become part of the standard toolset that most Lisps provide. For example, the Lisp Machine had a List Callers command that would show you, and then let you visit, every function that called a given function. I worked at a place where we reimplemented that functionality for ourselves, by poking around in the internals of Allegro, but AFAIK no Common Lisp comes with this feature. It's too bad, I think, though admittedly grepping the source tree is usually an acceptable substitute.
SLIME has been using that since 2004, ILISP has had who-calls since I don't know when, likewise Lispworks and MCL. Allegro has it too, since at least 1999 according to usenet (it's the :who-calls top-level command).
This article is from 2009. Clojure was not as well known as it is today, otherwise the author would certainly have mentioned it, because he came from Java. There is one commenter who mentions it, but it didn't pick up.
http://www.tfeb.org/lisp/mad-people.html