I <3 Martin and the team that built it. It's great to see that the Rust stack they used is the one I contributed to, now 8 years ago. Aging like fine wine!
Books which I have read and would recommend include:
- _Ashley's Book of Knots_ --- everyone should be aware of knots and now at least the basics interesting, _The Klutz Book of Knots_ was also mentioned once
- James Clavell _Noble House_ --- part of his "Asian Saga", not sure if it has aged well --- if a person could read only one of these, I'd recommend _King Rat_, based on his experience in a Japanese prison camp in WWII.
- Hesse _Steppenwolf_ --- that Hesse is no longer read saddens me deeply, and not just because this makes _The Glass Bead Game_ less likely --- his thoughts on the difficulties of interpersonal relationships resonate even now
- Knuth _Literate Programming_ --- I _really_ wish this style f programming would gain traction and that there would be more instances of taking famous programs and re-writing as a Literate Program, e.g., http://literateprogramming.com/adventure.pdf
- Knuth _Digital Typography_ (and not just because I have a reward check)
- Knuth _Mathematical Writing_ --- if you do any work in math, you probably already have a copy --- if you don't, you probably need one
- Dewdney _The Planiverse_ --- response to the classic _Flatland_, this has a real charm and despite the dated computer technology, has held up well
- Walter jon Williams _Hardwired_ --- an amazing cyberpunk novel, part of which was published in _Omni_
- Steven Brust's _Jhereg_ --- one of my favourite fantasy novels, which I've been reading since picking it up in a Waldenbooks when I was in high school, waiting for the last two books, and esp. glad of these since they made the "Paarfi Romances" exist --- anyone who enjoys Alexandre Dumas and fantasy should read _The Phoenix Guards_
- C.J. Cherryh's _Regenesis_ --- her entire Alliance--Union series is amazing and books are so varied pretty much everyone will find something which appeals
- Trevanian _The Eiger Sanction_ and _Shibumi_ --- not sure if this and _Shibumi_ have aged well or no, but the latter was a big part of my childhood
- Ben Franklin's Autobiography --- read presidential biographies to my kind in chronological order as a trial and regret not continuing with the actual project: biographies of important persons in chronological order
- Hal Clement _Space Lash_ now available in https://www.goodreads.com/book/show/939760.Music_of_Many_Sph... --- I recommend folks read it in reverse chronological order, starting at the back, then working to the front and bailing when things get too quaint/old-school/golden-age.
- _Foxfire_ --- a classic series what predated the "Maker" movement
- Tolkien's _The Fall of Arthur_
- Knuth _TeX: The Program_
Books which were sufficiently striking that I have made a note of them to get to read (hopefully this will work out better than _The Black Swan_ which I found annoying)
- _Visual Thinking in Mathematics_
- _Hardcore VisualBASIC_ --- still a bit bummed that I managed to miss this and MacBasic....
- _Phoebe and her Unicorn_ --- getting this for my daughter
- _Harmony with Lego(R) Bricks_ --- book on music improvisation
- Ornamental Origami
Note that a number of books weren't actually mentioned, e.g., Isaac Asimov's _Book of Facts_
I'm not reading a solid argument as to not use "..Defaults()" because doing so suggests that you may introduce a bug and therefore should be explicit about EVERYTHING instead? Ugh. Hard disagree.
Using ..Default::default() means “whatever additional fields are added later, I don’t care”. Which is great until someone needs to add a field to the struct, and they rely on the compiler to tell them all the places that don’t have a value for the field (so they can pass the right value depending on the situation.) Then the callers with Default are missed, and bugs can result.
Any time you say “I don’t care what happens in the future here”, you better have a good reason for that to be the case, IMO.
It's really unfortunate that Default is often interpreted as "recommended" when the trait makes/requires zero guarantees beyond the value being a valid member of the type.
We have similar interests! I've been working on a DIY animatronic project that is mostly vibe-coded using Sonnet 4.5. It's my first electronics project. So far, I got the Ultrasonic Sensor to trigger led when object is less than 2 feet away. I set up a sound player and the components fried when I started the device. I have to redo all of the wiring for the sound setup again. I only have one of three sound modules that isn't bricked.
The comments in this thread reveal a community of parents who are aspiring builders of high tech devices for their children. I think this community need a discord.