>>12388960>Software engineering is too light on math and you won't learn advanced concepts needed to get into fields like image processing or cryptography.>>12389699>Not OP, but what math textbooks would you recommend I read in order to be a competent programmer?I'll get a ton of shit for this since this is the math board (I used to be a /g/ native but it's unusable now), but I'd say unless you're trying to get into math-heavy fields (graphics/rendering, signals processing, cryptography, some ML, etc.): none.
I'd say you don't even need math skills to be decent with standard use of crypto either; only if you're trying to attack or implement cryptographic implementations or design your own algorithms. I work with crypto a fair bit and I can't even do basic algebra.
It of course varies a lot by field, but I'd say for 95% of software engineering jobs, you don't need to know anything about math beyond very elementary basics. Like what an exponent and logarithm is, base 2 (binary) operations, how many seconds are in a minute (most actual math an average dev does is probably related to time), and as
>>12389713 mentioned, set operations are very helpful to know (but it takes like 30 seconds to learn all the ones you'd ever use while programming - pic related is 100% of what you need, and don't even bother memorizing the symbols).
In terms of just being generally competent working with data and being a functioning human in general, statistics is always good.
If you're just working a typical software engineering job, focus all your effort learning actual software engineering practices, as well as the practical things like languages, tooling, library and framework ecosystems, workflows, idioms, etc. That'll help you most, by far.
And just spend as much time as possible working on different things. It's like getting good at music - you just have to keep writing code for years until it becomes intuitive.
