Hi, great write up and very cool project! I was wondering how you arrived at the idea to use OSRM and pre-computing the drive time from every exit to every POI. Was that something you learned existed along the way? Did Claude/codex point the way to this?
> “ Three factors were required to join this holy ensemble: the technical expertise to design a capable and reliable microcomputer, a nose for the larger business opportunity latent in the hobby computer market…”
I think the same opportunity exists now in the hobby robot market.
My 7 year old loves it! He likes the animations, how the creatures get the questions wrong sometimes, and the math questions. Questions were - why do we play a wizard guy (he wants to play as different characters), why does the scorpion drop a star, why are some of the moves not available / charged up yet
Sounds like you just need interview practice. (Your post seems more about interview nerves than ADHD issues). It’s a different skill, separate from being a good coder. It’s difficult to tell from your post if you have had any interviews yet. You mention “I've never had a real interview after college”. I would specifically look into getting mock interviews where the stakes are low, and get feedback and practice, so you learn how to improve and gain more confidence. You can ask friends, watch YouTube videos (for ideas, but this is not real practice), go to college career networking events, or search for “interview practice” - there are companies and services that offer this. You can get good at this! Good luck!
Just to provide some counterpoint to the echo chamber here - as a Dad of a six year old who played with legos as a kid and again now, I can affirm - Legos and the sets they put out now are way cooler now than when I was a kid!
You might worry that the less general purpose, specialized pieces might stunt creativity, but guess what!? The 6 year old has no problem taking them completely apart and building something off script.
It's the olds who worry about keeping them all together and not losing the pieces so they can still make the thing on the front of the box. The kids don't care and will happily take it all apart and build things we never would have thought of.
No one uses API keys with Copilot intentionally. If you install the VSCode extension and start using it, and you happen to open a file that has an API key in it, boom - it's sent to Copilot. That is the issue. It's currently like walking a tightrope with no guardrails, and it's not obvious.