I guess the thing is that for any bit of reasoning, “there’s math for that”. So whether it feels like you’re using maths or not, you are.
Restructuring code, for example, often needs a good grasp of negation in logic.
Do you need formal training to do it? Not really. It’s advantageous to have a good math grounding though. My colleagues that have a good math education can often reason and communicate using graph theory, especially when it comes to architecture. Set theory is also super useful - I’ll often see people writing crappy algorithms because they don’t know about using sets (again, understanding computability and complexity would have helped here).
Maths is all around us, it is really just the study of patterns after all. That applies more so in software, even if it’s not immediately apparent.
Restructuring code, for example, often needs a good grasp of negation in logic.
Do you need formal training to do it? Not really. It’s advantageous to have a good math grounding though. My colleagues that have a good math education can often reason and communicate using graph theory, especially when it comes to architecture. Set theory is also super useful - I’ll often see people writing crappy algorithms because they don’t know about using sets (again, understanding computability and complexity would have helped here).
Maths is all around us, it is really just the study of patterns after all. That applies more so in software, even if it’s not immediately apparent.