I've seen some lispers going 'full stack' programming. Clojurians (like this guy http://www.learningclojure.com/2010/09/clojure-is-fast.html) also aim to cpu cycles when they program. It's an interesting workflow to prototype high and fast and the project it down baremetal.
The fact that Lisp systems have traditionally included an easy-to-use asm inspector right in the environment is an interesting aspect imo. It's actually more common in my experience for Lispers to look at their generated asm than it is for (non-embedded) C coders to do so, because it's so easy to just (disassemble #'foo).
It's indeed nice to have direct connection between high and low. It's also in lisp culture to unfold layers of code transformations rather than stay in your own isolated layer and relying blindly on 'external tools' that will never be as integrated syntactically and systemically as ... well lisp.
Lisp aside, having this point of view seems to be a good goal to reach.
ps: There's also one very important lower layer, the memory/cache subsystem.
