Earlier quoted context omitted.
I was a mechanical engineer before I shifted to software development (so kind of the opposite of you) and I think you need actual, full on college level schooling to be a mechanical engineer in most cases. The stuff you're focusing on - basically manufacturing techniques - is a very small part of engineering in general. I didn't see any mention of CAD or FEA work, but even assuming you do know some of that or can acc…
Can I ask you a couple of questions? I am in a patricular situation, I'm a mathematician who does FEM and I think my training has been too abstract. My most recent work involves programming custom code in C++ for the study of buckling of thin shells (finite element method, continuum mechanics, differential geometry of shells, and all under the umbrella of functional analysis). Still the region I live in has virtually…
Machinery handbook rocks, but it is far from perfect. It's great for machining, it doesn't cover all of mechanical engineering. I've leaned hard on Roarks formula handbook through my career. A materials reference book goes a long way too. More recently referring frequently to degarmos manufacturing book.
I've used a cheap-ish Windows laptop for almost all of my research and design. CAD can suffer as assemblies get large, I turn fancy rendering off as it is mechanical engineering, not making prettying renders. FEA can eat resources fast. I've pushed to a beefier desktop as required. I've done some CAD on a tablet, but I hate the form factor for it.