Although the math in the book is relatively basic I enjoyed it tremendously because it gives the historical development for everything and even describes the characters of different mathematicians, etc. The historical context helps so much with understanding.
I hope people don't take away the negative side of the article, brain slows down, but the positive side: brain gets better with usage. Its uncomfortable, I can churn out programs as complex as programs I've already written and go to review meetings and planning meetings without much effort. But being able to solve PDEs reasonably quickly and accurately, I cannot, or have not without a great deal of practise. It's unconfortable in some weird mental but physical sense. But I'm sharper in everything else I do.
One interesting thing about software as career followed by math classes is that there's no compiler - you can type any janky thought into LaTeX and if you don't detect that it's bogus, nothing will, until you show it to a professor.
Also, the information density of maths notation is way higher than (good) code. We want code to be readable by some that doesn't know it; a lot of math seems to be readable when you sort of 80% already are familiar with all the prereqs. So no just skimming and then hitting compile/test/run (whatever validation you do). It's typing letter by letter and taking the mental effort to actually see and decipher the letter (at least, for me in my current stage; I'm trying to do novel research, but my demonstrated understanding of the details of the previous research is embarrassing low).
Also, weirdly, I still have the same fear of professors that I did as a young person. I manage it better with my decades of maturity (really) but it is still a part of my social interactions.
I will look into Lean that is mentioned here.
It teaches the basics and then how to build a MIPS processor.
I know that's only part of what nand 2 tetris aims for. But still good.
Much better than how I was taught in my schooling.