It's more like "If you're not checking that a creaky hand-rolled code-generator actually produces sane output, you'r not programming".
And yes: if you have performance issues with your Lisp code and you're not looking at the generated machine code (or more likely in the modern world, doing tracing to identify bottlenecks which are probably in the IPC or I/O layers), you're not programming well. Continuing to whack around in your REPL is doing just what the JP Morgan executives were -- ignoring the details of the real problem in the hope that the abstraction will be sufficient.
And all abstractions are leaky.
That's quite a generalization.Regardless, I'm not sure that CEOs should be told that "hey, you should definitely be micromanaging your team or you're not worth your salary" because some abstractions can be leaky when not designed well.
Layers of abstraction exist for a reason.