I think my wife and I have a toaster from when we first got married. It'll be 13 years this month. It's probably a 2009 or 2010 model, so really only about a decade or a little less old.
Every time I start a little thing in C or C++ and I write a corresponding Makefile I get annoyed by it and write the thing in Rust. Cargo is really nice. I've considered using a Cargo.toml and build.rs file just to build C and C++ files before.
This mostly works. After military service, I never changed back my cell number and I never answer if it is from the old area code. Though, I did once and it was a volunteer fire station asking for donations.
> We do all of our development in C# using a custom low-level “game engine”. At some point we need to do a writeup about it, it’s kind of interesting tech.
But I think they have at least one Unity game... or so I thought.
And, unfortunately, it is a destructive process going from elf to hex, as I've discovered a few times. Intel HEX is just the data at what addresses so one looses the section info and metadata from an elf.
I'm always happen to see when a uC vendor IDE keeps the elfs and the programmer takes elfs.
I learned by working at a contract manufacturer who also does engineering design of small device electronics (as an embedded engineer). I also have a copy of The Art of Electronics but I can't say that I've looked at it much.
This was the go to method of keeping information when I was in the military (05-09), which was _strongly_ encouraged starting in boot camp. If one was found without a pen or two and a notebook, there was some words said. I've kept the habit going into my civilian life though I don't take notes as often.
Others have mentioned that include_str! is a macro, which I suppose it is. But if you look at the source it says that it is a compiler built-in[0]. If you dig into that, you'll see that it happens inside the compiler[1] (well duh). I feel that that makes it slightly different than a normal macro in that it doesn't expand to a bunch of Rust code. I found that pretty neat.
Football toy chest! I had one of those. I remember climbing inside it -- being able to fit inside it even. I remember, when I was older, trying to climb inside but backing out because I was afraid of getting stuck in there (and trying to imagine how they would cut me out of the thing, that kind of gives me the heebie jeebies even now).
I second Duluth trousers. I had difficulty finding pants that fit since I'm a little shorter but have bigger legs. Getting pants with larger legs means a larger waist and a belt only helps cinch that up so much. Gusseted crotch trousers fixed all that. I've worn both the ballroom jeans and their khaki pants and they're both worth it.
A bonus is, if you're into martial arts, being able to kick above the waist or 'roll' (Judo/BJJ), you can still do so in those pants.
Yup. At my work we are doing embedded development and we use the Sparkfun FTDI breakout boards for UART communication. People have come to call the FTDI breakouts "putty boards" but in engineering, some of us use Kitty and call them "kitty boards". :D