But he is making of this more of an issue than it really is, this is really no big deal, because every mature programmer knows about that and that is easily avoidable.
Maybe. I'm surely putting Lisp under a microscope. You may see more bizarre things if you do this with an organism rather than a brick. And that's the point.
"Pascal is for building pyramids — imposing, breathtaking structures built by armies pushing heavy blocks into place. Lisp is for building organisms..." ― Alan Perlis
Currently, I use lisp to generate code in other languages, avoiding horrendous errors like SQL injection attacks. When I took a hacking course (yes, such things exist), they demonstrated that PHP coders are supposed to do a lot of tedious text escaping. Clearly, Lisp users avoid such problems because they're probably using some easy-to-use tool which Just Takes Care of It. I spent part of a weekend writing a little lisp tool which generated PHP/SQL automatically, with appropriate input validation and type inferencing. The code which came out of it was solid.
(Maybe I should slap a LispWorks GUI on it and make it available as a public service.)
Nowadays, I see so much public-facing code with SQL injection vulnerabilities that I don't bother to fix them. I simply point it out to whomever has decisionmaking ability, with the knowledge that it won't be fixed, and move on to the next zillion tasks. (But I don't "get used to it," like I don't get used to quoted literals' undefinedness, or how you have to remember to set *READ-EVAL*. Something in the back of my mind still voices annoyance at statistically trading correctness for.. whatever benefit which could be obtained in a better way anyway.. and I'm reminded that I still look at programming as an outsider.)
So, that is how I might put other languages in perspective, unmagnified. I use Lisp to correct deficiencies of other languages.
(But that said, I've seen terribly undebuggable Real World ™ code in Lisp. In certain dimensions, it may be the worst code I've ever read. Ultimately, the good thing about CL — it's a Big Ball of Mud — can also be the downfall of some poor codemonkey blinking at perverse uses of DECLARE SPECIAL. )