Per accident, normalized over velocity and angle of impact is ideal I'd assume in order to not bias on the kind of driving done in vehicles of a given brand.
Usually starts with "this can't be THAT hard to add this to my project, let's try it". Six months later you've got a solid working knowledge of running a lathe and you've started teaching workshops to other hackerspace folk on how to run it because everyone has seen you running that machine and needs help on it. Then you realize you forgot to finish the project that sent you down this road in the first place. You get bored and stop using the lathe for a few months. "Hey, it can't be that hard to design a PCB for this project, lets do some of that now..." Six months later you're teaching workshops on it...
And then years down the road you know how to make most things from scratch from the electronics design, PCB gerbers, and the enclosure both in metal (both machined and fabricated), laser cut, and 3D printed. But just conjuring up any cool thing you want to make summons a mental spreadsheet of the time it will take to complete the project, possibly including making a small-run of extras to sell for much less than your time is worth, and then you set your drink back down and shake your head because ain't no one got time for that any more. And then you buy the Etsy/Kickstarter version instead because you realize they have woefully underpriced their super cool widget.
You don't need a certification that attests your knowledge on the labor market when you are doing something as a hobby. I know it sounds weird, but you can just do it and fail and repeat until you can.
The hardest part by far is figuring out what you want to do. Even if you think you want to do a hundred different things and you can't do them all, you still have to figure out what you want to do.
With KiCAD and dirt-cheap PCB manufacturing, the PCB design is just a matter of starting with something simple. It took me a (long) evening to go from nothing to an VGA I2C Atari joystick controller board. [1]
Once you've got the hang of it, more complex PCBs aren't really that much different.
I started with double-sized PCBs, but 4-layer PCBs are now almost equally cheap, which makes routing a lot easier too.
Lots of entry points, but the best way is to just start a project that’s simple and learn as you go. Electronics have gotten pretty accessible with arduinos, rpi, circuitpython boards etc. machining does take shop time to learn. Friends, maker spaces, school shops, all are options but that’s hard. Sometimes you don’t need much to get going.
> I don't know how ABSEIL fares around exception safety when exceptions are enabled so YMMV there if you're doing things in an exception context
OMG this is my time to shine. I wrote the library for testing Abseil containers for exception-safety. I don't work there anymore but I know they've implemented exception safety tests for a bunch of containers in there, and I remember when I was writing the library we even found a bug in GNU `std::optional`.
As a side story, that talk was the first one in the morning and I showed up just before it started on account of my Uber driver missing the highway exit. I had planned to grab some food at the conference but didn't have time so that whole talk I was overstimulated on coffee on an empty stomach trying to keep my composure early in the morning.
I'm kind of surprised that ABSEIL even bothers with exception safety since Google builds everything without exceptions. Can you shed some light on why the team decided to invest in making it exception safe?
How would the world collapse? This sounds like mixing up "the world" with "human society". I know I do more when I'm happy because things are enjoyable. No disrespect to Don Knuth and it's obviously good to realize you're not gonna be happy all the time but that line of reasoning is just not true.
C++'s `std::unordered_[map|set]` has a requirement that the addresses of objects in the map don't change on a reallocation -- this forces it to use buckets with linked lists under the hood. Try absl::flat_hash_set (https://github.com/abseil/abseil-cpp/blob/master/absl/contai...) and see how it goes.
This is why we work with our tools though, no? A NN can decide where the ambiguities lie in the data set and communicate that to the data scientists who are working with it, who can then provide data to help disambiguate the data.
Outline (getoutline.org) is a super easy to use you run on a cloud server. No logging and it works everywhere there's censorship, and it's easy to share access to your server with as many or as few people as you like. The only cost is the cost of running the cloud server, a few dollars a month if you use LightSail or DigitalOcean. Disclaimer: I used to work on it.
I’m a fan of Outline and I ran my own DO droplet when the criticism around ProtonVPN and mail was happening, few minor pain points for me were the deprecated warnings that showed when booting the Linux client and it unfortunately presented me with the most connectivity issues. It would show connected but after doing IP lookups would reveal true IP. It’s seamless and easy to maintain but seemed unreliable at least on ZorinOS.
