Hacker News
Notes on Mathematics for Engineers (1959) [pdf]
ky3
|next
[-]
Family Spatial symmetry Example
------ ---------------- -------
Bessel Cylindrical (r,θ,z) circular drum, heatpipes, waveguides
Legendre (Ordinary) Axisymmetric Spherical (θ) earth's bulge spinning on its axis
Associated Legendre Full 3D Angular Spherical (θ,ϕ) spherical harmonics
Laguerre Radial Spherical (r) radial pdf of electron in hydrogen atom
stochastic_tn
|next
|previous
[-]
The beauty of math has played a huge role in the career choices that I’ve made so far. I changed fields at one point because I realized that the math that practitioners used was almost exclusively all baked into CAD tools. I figured that if that was where the applied math lived, then I wanted to write software for a living.
With a lot of the AI tools now (which I use and appreciate daily FWIW), I’m beginning to see that even in math-heavy sub disciplines of software engineering (e.g. robotics), we’re not exempt from this trend.
helterskelter2
|root
|parent
|next
[-]
He showed me some of the books from the 40's and 50's geared towards teens and honestly they did a better job of explaining things than the college textbooks I had to use -- they didn't go into fine detail, but they gave you a good framework to build on and a way of thinking about something which I feel is lacking from contemporary texts.
Tangentially, Feynman said something in a similar vein about the transition from analogue to digital. Kids couldn't tinker anymore and had no real impetus to learn some of the laws which underpin their workings, and most importantly, had no way to build an intuition around these laws through casual experimentation (i.e. fixing a broken radio with a handful of parts from Radio Shack).
Abstraction can be a very powerful tool, but growing up and learning in an environment which has these abstractions already built-in is a real handicap to building a deep understanding of a subject. You become dependent on the tools themselves instead of developing the knowledge used to build the tools -- in effect, the tools become limitations. Look at kids who grew up with iPhones instead of Amigas, or people already becoming dependent on LLM's.
annzabelle
|root
|parent
[-]
I've kept it around and used it for self teaching when I went down the rabbit hole of prepping for actuarial exams a year back, and again for prepping for going back to college to change careers to medical physics (yes, I have been looking at a bunch of different options to leave software).
I find it so much more elegant and straightforward than modern textbooks, and it's so much easier to focus on pen and paper vs screens. I've had people suggest Khan Academy and 3Blue1Brown, but I find I learn more deeply and retain better from a good old school textbook.
upboundspiral
|root
|parent
|next
|previous
[-]
As you note, all the Finite Element tricks are hidden, all the meshing tricks are hidden, and while you can find some in old research papers, in general the main companies hoard them.
The landscape has been 3 / 4 forces:
1) individual academics that do interesting work but more often than not abandon the codes they produce after a paper or three.
2) Proprietary companies that hire enough expertise to take academic research, generalize it, and sell a hyper-proprietary product with very little competition because the expertise is hard to come by
3) The national labs which do amazing work, that release a body of reliable open source work, though some of it is tailored to their systems - usually hard to use / very few people know about it outside academia.
4) Open projects like OpenFOAM / OpenCascade that struggle along at the edges to create a cohesive whole that can compete with the big companies.
I think that LLMs offer an opportunity free us from this status quo:
1) The open source work of the past is much easier to use / decipher with an LLM
2) The research is there, it just hasn't been productized (through an open source vector) / made accessible yet
3) I do believe that LLMs make learning the past codes / getting ideas for new codes / extending codes easier
I think engineering tools are up for a shakeup, as both LLMs + new paradigms are emerging. There is really interesting research into new meshing methods / CAD representation (Brep vs SDF) / topology optimization.
I believe this is an opportunity for an open source ecosystem to start making inroads into the bottom layers of the engineering stack (CAD kernels / representation), and from there make inroads into meshing + make open source FEA more accessible.
I am excited by what the future might bring, and remain cautiously optimistic that just like no one buys a programming language anymore, the lowest levels of the engineering stack might become open source so that research is accelerated, engineers are freed from total lockin, and in general the ecosystem is much healthier and innovative.
nimitbhardwaj
|next
|previous
[-]
melling
|root
|parent
[-]
nimitbhardwaj
|root
|parent
[-]
hansvm
|root
|parent
[-]
oldjohnnylane
|next
|previous
[-]
rustybolt
|root
|parent
|next
[-]
See https://math.stackexchange.com/questions/4752749/how-could-f...
jesuslop
|root
|parent
[-]
djfobbz
|previous
[-]
aleph_minus_one
|root
|parent
[-]
Reference:
https://althouse.blogspot.com/2024/12/during-cold-war-we-cla...