bathMarm0t
Joined 13 years ago
Joined 13 years ago
Cloudy. Raw. Fragrant. Sweet. Funky.
Absolutely delicious.
It also has almost no shelf-life (no acidity to protect, and sterilization destroys all the charm), so no one imports/exports it, but if it caught on in America I would not be upset.
http://wrightbrothersrc.com/products/gambler.htm
If the goal is the flying. You can't go wrong with an easy star. I've crashed mine a million times. You just patch it back together humpty dumpty style with thick CA + accelerant. Bonus points for the prop being in the back, so if you run into stuff you (probably) won't draw blood.
https://mrmpxhobbies.com/product/rr-easystar-3/
Note that the hobby does require some skill w/ flying and need some level of risk management. There are cords that let you plug your transmitter into a computer/fly over a simulation that can help with the former.
Option 2: Confront your mental blocks and shitty life with less depression (due to pharmacology).
Option 3: Confront your mental blocks and shitty life with a guide and less depression (due to pharmacology and therapist).
Option 4: Wait for the law of averages. https://youtu.be/3s_BqdZrUbE
I'm taking option 3 all day, every day.* (e.g. I agree with you. They should always be done in tandem / there is no silver bullet).
*It's very important that your therapist shares your zeitgeist or directly counters it as a devils advocate. The drugs... not so much.
If an idea doesn't work on the back of a napkin, it's done. Think about other approaches to the problem and get another napkin. I think that's what he's getting at. Analysis from first principles is hardly gatekeeping.
According to this one[1], they're adapting by leaving later, and flying faster/taking less breaks to make up for the lost time. The result being that less of them make it to the breeding grounds (6% decrease in survival rate).
[1] https://news.cornell.edu/stories/2023/04/risky-strategy-help...
The back pain was instigated by moving, driving across the country, helping someone out with yard work slinging rock, and then going for a post-thanksgiving run, which broke this camel's back. Lumbar shaping is very, very important for the lower spine. You can do it with muscles, or you can do it with things. I used a 10 dollar IKEA chair + grippy bottom + a rolled towel. You roll the towel until it's the right size to create a slight arch. No rulers or drill sergeants necessary. It's also important to note that the drive to/from work is doing just as much damage as being at work, so using the towel in the driver's seat is a godsend.
The wrist pain was instigated by working on a laptop during a 1+hr train commute. I kind of looked like Groot (Despicable Me) prancing around, minus the prancing. I tried pretty much everything, but what stuck was the Evoluent mouse. It allows you to use the mouse without arm pronation (pronation forces the carpal region into a binding/constricted position). It's ~100 bucks but a single doctors visit costs more than that.
Happy coding.
1. Yes they are microcontrollers.
2. Yes they use C/C++. (check the libraries/SDKs, 1 layer under the hood it's all .h/.cpp files, and most of the arduino calls are just #defines)
Bluetooth is an absolute nightmare if you don't understand the majority of what's going on (which in and of itself takes... a lot of time). There's a bunch of logic going on and most of it is handled in callbacks that you will never see, except the dreaded timeout/failure to handle print at the end of the main loop. Zephyr will ease a lot of those painpoints, with the understanding that you're ignoring a lot of the machinery humming under your feet.
Things that stood out to me:
0. If this is your first embedded project / you're actually new to all of this, get ready to take a beating. "Abandon all hope, ble who enter here."
1. Do yourself a huge favor and get two* dev kits. Nordic provides walkthroughs on getting setup with two flavors of code (zephyr, or low-level drivers). Each has a tutorial for uart forwarding/handling. Expanding on that tutorial will take a lot of futzing around, or actually learning what the machinery is doing under the hood. Learning the stack did not come naturally / I found it very difficult. Why two? Two lets the bluetooth abstraction handle itself / you don't have to deal with it right away when you're getting started.
https://www.nordicsemi.com/Products/Development-hardware/nRF...
2. If / when you want to attach your bluetooth device to something more useful (e.g. a computer or mobile device), do yourself a second huge favor and develop using linux + a laptop. I tried to do development on windows + WSL and there were many, many hangups with the hardware handoffs from PyBlues to the local bluetooth drivers. Maybe it's gotten better, but I doubt it. My other alternatives were driving direct from Windows bluetooth libraries (behemoths that would take time to setup / understand), or develop for mobile (which also will take time to setup / understand). Neither was an enjoyable experience.
so in summary:
Is Zephyr overkill? - Absolutely. But the path is well trodden.
Put on a good set of headphones and go sit in the corner.
Also obligatory: https://www.youtube.com/watch?v=Ah392lnFHxM&list=RDAh392lnFH...
The thing I appericiate most about bach is:
you can play it fast.
you can play it slow.
you can play it with an ensemble of random instruments.
you can play a single voicing all by itself.
all of it screams "musical". which, if you do play say, Tuba, or one of the larger instruments, is a godsend, as most of your lines in other pieces will bore you to death.