That is, one is probably more practical on a daily basis, but both sides depend on each other. You can't, meaningfully, have CS without programming (though maybe you don't program yourself and stick to the math parts of CS, you'd be in the minority of computer scientists who did so). And programming itself is informed by CS (directly if you're a computer scientist or have studied CS, and indirectly because all computer systems have themselves been influenced by work in the field of CS).
Also, "vs" sets them in opposition to each other in some way, when the fact is the line is very blurry. Your original analogy is one of opposition because "pizza research" sounds like the corporate research going into making Domino's taste more like a greasy cardboard box, which is hardly dependent on direct consumption (you bring in college students for that). Whereas CS and programming are closely intertwined, more like my marginally improved analogy with research and cooking.
In the physical domain I think a more apt analogy would be mechanical engineering vs. fabrication.
Some nuances:
1. by CS one can understand both the practice of using CS principles to design modern efficient computational systems, and also CS research.
2. programming alone would not get you very far, so a lot of people normally mean, programming + database knowledge + systems design when they are talking about somebody who does programming.
Programming is like working on some specific implementation of something related to producing a pizza: growing green peppers, or rolling out dough.