1. 24

  2. 13

    On a tangential remark, I’ve been enjoying going to a coffee shop after work and learning and re-learning mathematics and physics in order to continually stretch my mental capacity. It helps tremendously with stress management at work itself. I feel more capable of taking on enormous, difficult tasks at work because of the challenges I face in remembering how to tackle these math and physics problems that I faced in college. I started doing this about a month ago with a geometry textbook. I’m up to Precalculus now, about 10% of the way through the Precalculus textbook by Stewart. I’m planning on going through Calculus and onto Classical Mechanics, followed by Electrodynamics and Quantum Mechanics. (I really do want a good challenge!)

    1. 7

      You’re lucky. After eight hours of programming/meetings the last thing I want to do is program or do match. After some dinner with my SO, I go straight to reading (never tech stuff) or video games.

      1. 1

        For QM I would recommend Shankar just for the intro section on linear algebra, although most people seem to prefer Griffith’s for the actual QM stuff.

        If you like type theory or algebra (the grown-up kind), I can PM you a link to an early WIP draft textbook from one of my former professors that covers classical mechanics in an exceptionally mathematically rigorous way, with full coverage of the algebraic properties of different physical quantities and systems. It’s actually for a simulation course, but it’s better for learning classical physics than any physics course I’ve taken.

        1. 2

          Thank you for the suggestion! I have read in a few places that reading multiple QM books is common. This is the list of books that I’ve got lined up.

          • Precalculus: Mathematics for Calculus, 6th Edition by James Stewart et al. (Amazon link)
          • Calculus: Early Transcendentals by James Stewart (Amazon link)
          • Classical Mechanics by John R Taylor (Amazon link)
          • Introduction to Electrodynamics by David J. Griffiths (Amazon link)
          • Mathematical Methods in the Physical Sciences by Mary L. Boas (Amazon link)
          • Introduction to Quantum Mechanics (2nd Edition) by David J. Griffiths (Amazon link)

          My biggest concern about this list is which order to read the last four items in. I was thinking of starting in the order listed, but I may end up having to jump around given that there is likely going to be overlap between them.

          1. 3

            For what it’s worth, during my undergraduate studies in Physics, Mathematical Methods in the Physical Sciences and Classical Mechanics were taught for two semesters each, in parallel. In the second semester, alongside the two, we’ve had an Introduction to Quantum Mechanics course (mostly as a conceptual and historical introduction, no very advanced stuff). Finally, Electrodynamics and a “full” QM course followed the year after.

            (There were a lot of other courses in parallel, but these are the relevant ones to your listing. You might want to add a Statistical Physics / Thermodynamics textbook in there for good measure. :))

            Try checking out the curriculum of a few undergrad courses on universities near you to get a feeling for a reasonable order of reading.

            1. 1

              Muchas gracias, amigo. That is a most excellent idea.

        2. 1

          What do you mean when you say go through? Do you do all the problems? How do you decide on problems to work if you do any at all?

          1. 1

            Anything that is difficult to grasp I’ll review it by going through enough problems until I feel comfortable with the topic.

            I’ll go back and review fundamentals to re-enforce dependent material, too.

        3. 2

          While I agree that you can learn a lot of technologies one works with, there is a thing you probably won’t learn like this: New ideas. Which is completely understandable, production environments can’t afford that. Only the very few technologies that survived for a decade or so do eventually get adopted for work (bar some exceptions). I’m talking about things like Idris, Elixir, Nix, Rust, and more, all of which have some great thinking behind them.

          1. 3

            Rust was developed at an organization that wants to use it (Mozilla) and has been adopted by companies that want to use it (e.g. Dropbox). I know companies that have used Nix. Elixir is also used by real companies.

            1. 5

              I’ll “me too” on this one. Where I currently work we have quite a bit on Rust in production. There’s a little bit on the cloud side and a significant amount on our hardware product (embedded linux box).

              The last place where I worked had Elixir in production too. Just a little bit in a mostly erlang codebase.

              1. 0

                While Rust has seen some adoption recently, on a global scale it’s pretty insignificant

            2. 3

              Why couldn’t you learn those things at work?