When I think of digital signal processing I think of things like audio and Fourier transforms. In my experience there's quite a bit to graphics programming that's different from that. A lot of shader code is linear algebra / matrix math, and physics equations for light. There's also a lot of thinking about memory layouts and how to reuse calculations as much as possible.

I say this as someone who does a lot of graphics programming in my job but failed "Feedback Control Systems" the first time through.

I did a double major in college.

In my computer engineering courses, I learned digital signal processing, and then took a follow-up course on signals and systems because I enjoyed the material and I had an eye on robots, because robots are dope.

Imagine my surprise when I got to 4th year and I suddenly found myself using the exact same math to handle thermal and fission product neutron poisoning feedback in my nuclear reactor physics courses.

Try explaining the physics behind any graphics or sound application without using the name Nyquist

Any electronic thing

"Hey, this thing I like is really cool, I wonder how it works?"

Math, loads of math. It is always like that.

do be

why not just say "is" instead?