Analyzing a failed drill bit with an electron microscope [video]
youtube.com
youtube.com
- It makes the drills harder, but as a result likely also more brittle, so they may only be "stronger" for certain applications
- Using the bit properly is much more important than what it's made of/whether it's cryo treated - he got an entire plate of steel with one bit with 30 m/min (and the bit was still good at the end) and then destroyed 7 bits, included some treated ones, on fewer holes than that using 40 m/min (I assume that's surface speed).
- This also means he didn't test how much longer the bit would last under good conditions, only that it was able to withstand non-optimal conditions longer. While it's likely that this transfers, it's not guaranteed.
That could have been interesting non-destructive scan with microfractured elements like this drill. They had them at uni. They had a third wire to ground after the test and some strange holding grip to prevent the whole setup from becoming a capacitor. One run took hours and you needed the 3d model of the object and thorough cleaning and sometimes sanding of the surface.
Clough42 is one of my favourite channels, always look forward to his reliably weekly video. Great mix of machining (metal), 3D printing, and electronics - CAD too which many don't show (and at just the right speed IMO, doesn't belabour it, but his narration of key presses basically taught me Fusion360, always in my head when I use it myself).
Of course there are loads of (perhaps better even) F360 tutorial videos on Youtube, but the nice thing about his is that it's just part of it - I actually haven't seen anyone else design & make - and it's entertaining, even if you don't want to learn or already know, he just treats it like any other thing he's doing.
Anyway, I just subscribed.
When I went to grad school for a Master's at an engineering school which, at the time, was small enough to not actually have formal departments, I studied a fair bit of mechanical engineering but actually did a materials science thesis.
Tldr; it's a lot of coursework but I've never regretted it.
I'm a TPM now, have worked on aerospace projects with small teams where it helps to be fluent in both sides of the electronics and mechanical design. I've managed multi disciplinary design optimization efforts where there is heavy intersection between code and real-world mechanical factors (writing code for my mechanical designs and writing the backbone for other contributors or translating their system to code). Being able to understand electric motor systems design end to end through the entire chain from control comms to firmware to MOSFETs, electromagnetics, and mechanics has been rewarding for me as well.
In terms of opening opportunities, small hardware startups are where I've been able to have impact, and where there is demand for someone who wants to contribute in both areas. Where I am now as TPM is a fairly limited track and PM is a bad word in some companies. At faang, it seems that software track pays better than tpm or mechanical so that is one item to note.
At larger companies it is a difficult sell for someone who wants to do both at the same time as an IC. Smaller niche companies are more likely to want someone who has the breadth and can help fill in gaps or own a whole project.
The reason I am not a pure SWE is that my passion lies in being able to hold the result in my hands at the end of the day (or week, month, year:)
I'd recommend you try out the machine shop or what is available to you if you go to an engineering college, maybe some robotics projects, mechanical engineering foundation courses, material science courses. See how you like it. I'm sure you will be successful whatever you do. If you do both it's a lot of work but I never regretted it for a second.
So, if you have the capability, certainly go both... It will give you, at your age, the ability to build the change you want to see in the world....
You could just take some of those extra earnings and take up MechE as a hobby.
Maybe if you are a MechE working for facebook or twitter. But go to something like SpaceX or BMW and you will find the best MechEs paid way more than the software people. The insane paychecks in CS only exist at companies where software is the final product. Companies that produce physical products put CS into a support role. A department head at Boeing or LM is far more likely to be from an engineering background.
For the record, I have an ME undergrad (and a grad degree that's basically material science) and while I've mostly only used my direct classwork a bit, I've done fine.
And the idea that basically any other engineering major will make 20% of an even remotely typical CS major is idiocy.
And at the end of it, you get a sweet perfect vintage car to show for all your learning.
DC electronics, motors, suspension tuning and theory, PWM, basic mechanical “instincts”, soldering, how transmissions work (some models had even fluid-filled torque converters on them) differential gearing (and some had limited slip!) and even regenerative braking.
Years later I’d constantly be surprised how all of these things worked almost the same way in real cars.
The rest makes sense. Controls are in different places, everything is bigger, but the basics are the same.
Is the bigger plane easier in the sense it is less twitchy?
I’ve tried a couple of RC helicopters and the larger one was much easier to handle.
You will see a lot of articles marked [PDF](somesite.com) indicating that the doctype is PDF rather and the default html page. There may be other doc types like that but those are the most common. I have not notice a list of possible values anywhere.
i get the label for [PDF] and what not, but does anyone think a link to youtube.com is NOT going to be a video?