Languages, whether natural (such English, French, or Russian) or artificial (such as Esperanto, Lisp, or Resolve/C++), are frameworks for expressing ideas. In particular, computer languages are frameworks for changing the state of finite state machines in order to make them do some kind of nifty stuff.
People who know one language, or two, or even three, are not programmers. Programmers understand what programming is about and should be able to program in any language given them. You don't take 221/222/321 to learn how to program in Resolve/C++. You take that series to learn how component-based programs work. You don't take three quarters of "how to use Resolve/C++" -- you look at problems and how to solve them using software components. The fact that you're using Resolve/C++ is completely irrelevant to the main point.
As I understand it from reading the papers that are available on the web, the series basically works like this:
What you do during the course of the 221/222/321 series, however, is to get yourself exposed to all of the main concepts of modern software engineering. You take a tour of what all of this "object-oriented" and "reusable software" stuff is all about. That means you're going to write better code if you can manage to apply those concepts to yourself and to your programs. Your C is going to be better, your Java is going to be better, and your Lisp is going to be better for having entertained the kinds of thoughts that were presented in class. You're going to be able to look at problems and more quickly recognize when something belongs in the program that you're writing and when instead it belongs in some more general-purpose library that is available to others, or at least to yourself at a later time in another program.
There's no guarantee that you're going to be using the languages that are popular now in five, 10, or 15 years. Languages, for the most part, just don't last that long. Languages like FORTRAN and Lisp are notable exceptions, but even they are very different languages today than what they were 20 or 30 years ago. That means that you're always going to be learning new languages, learning new techniques, and learning new features of languages you've been using. If you're not looking forward to a career of constant learning and rehoning of your skills, do yourself and the industry a favor and just quit now.
What you will have learned in 221/222/321 are more important than mastering
any language. They're the concepts that will make you a productive
programmer no matter what language you're using. That's the kind
of education that's worth basing a multi-decade career on.