This may be a difference in learning preference, but I've always found the easiest way for me to learn about new topics was to jump into them directly. Supplemental reading could certainly help of course, so I apologize that I have nothing to provide in that area, but if you're interested in it I'd recommend just jumping in with simple projects and learning on your own from there- with assistance from just searching around for fundamentals on google. I hate to be the quote person, but I think this one fits perfectly; "The best time to plant a tree was 100 years ago, but the second best time is now" or "A journey of a thousand miles starts with a single step". Ignoring the cliche quotes, I'd just say the best thing you can do is dive in without any direct guidance and navigate the unknowns yourself. At the end of the day, starting off in the wrong direction is better than not starting at all. Good luck on your adventure!
Thank-you!
The homebrew community that grew around it was also legendary. I learned Java (via LeJOS) because the block based programming became too restrictive for what I wanted to do. I learned C (via brickOS) once I hit code size limits with LeJOS and became less scared of pointers :)
I learned Java because of leJOS too. I wanted to display something on the screen. The rest is my career.