2,296 karma · joined May 2, 2014
Get in touch:
frtherien@gmail.com github.com/auxym
I like it so much in fact that I've been looking for a linux alternative and haven't been satisfied yet. I will try evince though.
Cannot confirm from my experience though, I don't practice EE, I just dabbble in electronics and never actually characterized SI and EMI in my creations.
Besides 80s computers which were truly simple, perhaps it would be interesting for you to first learn about microcontrollers. 8bit ones such as AVR or MSP430 would be simplest. They can still be purchased, and for relatively cheap, so you could run your own code and explore as you wish.
https://embeddedartistry.com/blog/2019/04/08/a-general-overv...
Note on Arduino: they consist of two things, hardware and software. It's a fine way to purchase a working board with an AVR microcontroller. However the software part (Arduino IDE, Arduino "language", associated libraries) are all made to hide the complexity of the hardware and make it as easy as possible to run code. This is quite fine for many people, but maybe not you.
I occasionally teach a strength of materials class, for mechanical engineering students, as a contract lecturer (my main job is research).
I love starting the fatigue part of the class with some historical context such as the Versailles/Meudon train accident (https://en.m.wikipedia.org/wiki/Versailles_rail_accident). I think it really helps to motivate the content and how the "laws", which can be sort of dry and boring out of context, came to be discovered by scientists and engineers who wanted to prevent these kinds of accidents from happening again.
Mechanical engineering consists of learning tools for analyzing designs, such as fluid mechanics, materials, solid mechanics, thermodynamics, statics and dynamics, control system theory, etc.
https://git-scm.com/book/en/v2/Git-Internals-Plumbing-and-Po...
It made me understand how simple git really it under the hood, you just need to understand how the commands operate on this simple data structure.
I second this feeling. OnShape was founded by the original creators of SolidWorks before it was bought by Dassault. It showed great promise in being efficient, powerful, user friendly, built in PLM (SCM for CAD basically) and surprisingly low cost. Compare hundreds a year for a fully loaded OnShape seat subscription to about 20k/yr/seat we paid for CATIA and some bells and whistles (PLM, FEA, etc).
The day OnShape was bought was PTC/Siemens is quite comparable to me, to the HN feeling when Adobe recently announced the purchase of Figma.
I can't remember the next part exactly, you can look it up in a textbook, but you multiply the matrices KMK, or similar, and the eigenvalues of this are the natural frequencies of the string. The eigenvectors represent the mode shapes, ie the displacement of each mass element.
The same technique is used in Finite Element Analysis to find the modes and modeshapes of complex structures (a car frame, a bridge, etc)
I mean, we do have the RCMP and Bay Street, but I don't think it's comparable (in number of positions, salaries offered, etc) to NSA and Wall Street.
I'm really liking Nim as a hobby these days. It has a very powerful macro system, which might interest OP. Nim macros basically normal nim code, executed at compile time by an interpreter built-in the compiler, which can directly manipulate or generate Nim AST.
Macros aren't exactly easy to read or write (again, it consists of manipulating AST nodes directly), but they can generate any amount of boilerplate code you need.
STEM is pushed hard, but realistically, science and math dont have that great career prospects. For one thing, a PhD, and the 4-7 year opportunity cost that comes with it, is pretty much required to get anything more than a lab tech job.
After that PhD, where do you go? You can try for an insanely competitive tenure track faculty position. Or a very limited number of industry researcher jobs.
The E in STEM (traditional engineering) isn't exactly tech in terms of salaries and job availability, but it mostly guarantees paying the bills with a decent WLB after "just" a bachelor's.
I worked as a structural analyst on passenger train cars (metros, LRVs, etc) for a while, as my first job after grad school actually.
Depending on the project (client requirements), we designed for 25-35 year lifetimes, with 12-24h operation typical. That usually amounted to millions of kilometers.
We had load cases with varying numbers of cycles. Eg curves with light loading might have been millions of cycles, but max (or even over max) loading might have been 10s or 100s of thousands of cycles.
All load cases were determined based on on usage stats from the operator and testing conducted to measure accelerations on the operator's infrastructure.
But I definitely do remember the era of cold cathodes:)
ORC adds runtime GC only for cycles, and will be the default in Nim 2.0.
On the good side, compared to go, Nim's interop with C is fully transparent (since Nim uses C as a backend). This means easy access to C libraries, but also makes it very appropriate for embedded targets like microcontrollers (especially with its ARC memory-management system, which is static/deterministic automatic reference counting).
I think it's just that every smartphone, tablet, laptop, etc now has BLE integrated, so it's easy to make a widget like a soil moisture sensor and connect it to your phone. Also, the newer LE version of bluetooth is quite power efficient so it can run for a while on a CR2032 if you take care to put the MCU in sleep mode between measurements, and whatnot.
The situation is quite rough indeed.
I do agree though, as you and many other people have in the comments, just getting a numeric Mbps rating would be way better than the 3.1 x2 gen 4 nonsense.
In fact body work in general on cars tends to be way more expensive than mechanical work.
I agree that TeX's errors is one of the worst things about it. Strongly suggest you track your changes in git, I found it was often easier to go back to some version that compiled and re-add the changes, rather than try and track down the missing bracket or extra backslash that broke it.
I'm so glad we can order from mcmaster here in canada, even though shipping is two days and usually min 30 USD even for tiny orders. All local industrial suppliers are truly stuck in the 80s. They have a paper catalog, without prices (if you're lucky you can get a PDF too). If you want prices, you have to call a salesperson, or send an email with an item list and wait a day or two to get a quote back. Then you get your quote, and some items are in stock, some others in stock "nearby" (next day delivery), others are backorder (1-X weeks). Then you have a lengthy phone or email back and forth to try and figure out what's in stock as a replacement.
So yeah, McMaster whenever possible and I'll gladly (have my employer) pay more for it. Shout-out to Misumi, too, however. I do mostly prototyping and I use so much of their customizable items, like rotary shafts. Much cheaper and faster than doing a drawing, sending it out to 3-8 local shops to try to find one that is quiet enough jobwise to take on a tiny one-off project and waiting 4 weeks for it, at a high price.
It was pretty dumb, using the exact "algorithms" we were taught to do it by hand. It would even "show the work" so I could transcribe it. In the end, it probably took as much time to input the homework into the program, and then transcribe all the answers, making sure to fake it so it looked like I did the work, as just doing the homework. Not to mention actually writing the program, but that part was really fun. I remember turning on a small night light when I was supposed to be past bed time so I could scribble down algorithms or solutions to bugs on a piece of paper so I could implement them the next day.
If I had been a bit smarter, I might have realized that I could have used a CAS that already existed. Not sure if there were many open-source ones (that could run on windows) back then (2003-2004) though, just looked and sympy was released in 2007.