The statement is pretty backwards. Sure a user may never look at or touch your code, but that code renders a visual interface in the browser, that either is or is very similar to what they will ultimately be interacting with.

Additionally, it implies that other methods of designing are "closer" to the user's experience, but a user will likely never see your static comps or whatever else you create to hand off for implementation. And since those things are inherently not the thing your user will ultimately be interacting with, they are in fact, farther from the user's experience than rendered code.

Command line is no longer used by the general population because GUI is a far better user experience.

Code has nothing to do with command line vs GUI.

You don't need to interact with code to have it effect a users experience, a users experience does not have to be interactive, for instance: is an app or site that runs below 60fps or has networking problems good for the users experience? No. you fix this with writing good code.