↑ Teaching myself programming, I can at least concur that I have used very little "extreme math" in almost all the projects I've done. It all really comes down to logical problems like "if this then do that" in whatever syntax is required by a particular programming language. I think it's the most empowering thing you can learn with regards to computer work, since it can translate into personal projects as well as a career. When I need a simple task or tool for a VG server, I can just create it myself and have some new button or executable to instruct VG Admins to use. Took years to slowly learn, but when you are driven by personal motivation, it's much easier.
Check out this, some programming can look like this and it's easy to look up any of these things online for more info once you know where to look. I'd say some of the craziest math in any of my programming projects merely amounts to number conversions, and for that, I simply googled my problem and had an example I could easily follow and apply to my needs:
elapsedTicks = Math.floor(currentTicks - previousTicks)
elapsedDays = TimeSpan.FromTicks(elapsedTicks).TotalDays
elapsedMinutes = TimeSpan.FromTicks(elapsedTicks).TotalMinutes
(programs can tell time in "ticks" which is a very accurate measure for elapsed time, where one millisecond is 10,000 "ticks" - here I use a previously save value of elapsed "ticks", subtracting the current "ticks" to get elapsed time, and then had to look up some maths on Google to convert that to seconds/minutes/days of elapsed time using pre-made functions embedded in the C# "Math" library). So, you can see here in this example that I didn't even "do" the math myself, I just used pre-made functions that are part of this programming language already.
Later in that program above, I can recall the variables "elapsedDays" and "elapsedMinutes" to refer to how long the program has been used for (this is part of the timer for limited use beta tests, for control of my versions etc.)
This is an example of a C# ("C Sharp") snippet from my voice control stuff -- this is the sort of stuff you may use in programming, some conversions and equations that turn one number into another, and unless you're creating physics engines, it's prolly not gonna get too deep on you. There are some people that can keep all this stuff in their head; personally I'm an amateur self taught tinkerer, and I pretty much rely on methods or snippets of stuff I find online and change/alter to my needs, or I use examples from previous works I've done that are similar (and again, change it up for whatever I'm working on at present).
Like others have said here, programming is like working through logical problems to achieve a goal, so I personally think it's very rewarding (even if dull and boring at times) because it's essentially problem solving.
Another example of the type of math that may be needed - I had a problem when I created my rotary dial controller for BMS, once it circled back around, all the numbers were wrong and the dial in-game jumped all around. I needed to correct that rotation to "reset" once it turned a full 360 degrees (back to zero) so it worked properly - and for that I had to apply some basic math, but nothing too extreme or crazy:
//Correct Rotation within 360 deg.
if (val < 0) {
val = val + 360;
}else if (val >= 360) {
val = val - 360;
}
return val;
This little function let me provide the value, and it returned the value corrected within a 360 degree range ... if it was too high, it subtracted 360, if it was below 0, it would add 360. Not so much hard math as logical problem to sort.
I think it's important for you to sample a little bit of each of these jobs before you decide which one interests you enough to keep driving you forward, see what they do and what that looks like, and talk to more people in those fields if able. I hope we have some more career computer guys here with actual jobs in these fields who can post up advice. I had a personal passion to learn programming, because when I was a young man in my 20's with an interest in computers, someone told me, "You were bad at High School, you'll never be able to learn the math you need to learn computer programming". IF I COULD GO BACK!! I would only tell myself to dive right in, avoid certain types of programming that require calculus-levels of math, and focus on object oriented programming and application development.
It's really not that hard once you get down the basics, everything builds on previous knowledge, so you start out small, and within a few years you are blazing through thousand line scripts to make your visions into functional reality.