Experience always varies!
My degree is in Electrical Engineering, where things get done. Sure, it has lots of math involved, and I did get to write a program or two to solve some lab work, but the best part was that I was employed at a university "up the street" that I wanted to get into, but didn't have the grades to do so. It yielded an interesting mix of things as I interacted quite a bit with graduate engineers who were actually doing things (and solving problems) using a computer. As an added bonus, they paid me some money to do it. I ended up being the BOFH for a mid-sized 32 bit computer for a few years (I did PFY work before that) and was able to actually diagnose problems with the hardware and develop interfaces for stuff they had lying around, along with the software to make them play.
But that was the late 60's and early 70's when Fortran was king, and to do anything special you used assembler writing subroutines for the other Fortran jockeys you had in the shop. Later on I did learn C and true to form discovered that one can write Fortran in any language.
But... if you really want an understanding of computer languages, try Lisp. While I haven't used it, the assembler I worked with used lists for lots of its processing, and you could do lots of things with it. Another language to try is Forth. Study how it works, and see how it is implemented at the machine level. On an 8 bit micro (which you should design/build yourself) you get to know LOTS of details that will serve you well in later life.
As for C++, I compare the books written by the progenitors of the languages. The book The C language and Bjarne's book about C++ differ by about a ratio of 4 in the thickness of the book. While not a very good metric, go and look at the examples. In K&R the examples are complete and well thought out. Bjarne's book yields examples that often finish up with "// ...". This makes the language more difficult to understand and reveals that C++ is a moving target that is (probably) more complicated than it needs to be (kitchen sink?).
So, while you might not need it, an understanding of low level constructs can prove to be very insightful. Learn some. Make some lights blink, read some buttons, solder a bit, experiment. It will prove useful.