misterAxiom
It's like Teen Talk Barbie.
2. All programmers should learn Galois theory, not only to get over the idea that they can't be good at math, but to learn to appreciate math. The book by Ian Stewart is good, although I would supplement it with Artin or Dummit and Foote.
3. Try to figure out why Ken Thompson and Dennis Ritchie did what they did, when they did it. Very important for getting a historical understanding of programming. Also, try to figure out why Ken Thompson said what he did in "Coders at Work".
4. Read The New Hacker's Dictionary.
5. Read Naive Set Theory
6. Try (and fail, at least for a year) to read A Shorter Model Theory (don't give up!)
7. Read Code Complete followed by the Python 2.x source code
8. Read SICP and write a scheme interpreter in a language of your choice
9. Implement a simple LR parser, instructions here: https://en.wikipedia.org/wiki/Simple_LR_parser
10. Play Kitten's game http://bloodrizer.ru/games/kittens/
11. Play the UC Berkeley CS 61a adventure game https://inst.eecs.berkeley.edu/~cs61a/reader/
12. Play JSRobowar https://statico.github.io/jsrobowar/
13. Read "Development of the C Language" https://www.bell-labs.com/usr/dmr/www/chist.html
14. Read "The Mythical Man-Month"
15. Read "Simply Scheme"
16. Read "The C Programming Language"
Now, if you have a lucrative opportunity, and you hire this team, then either the team will figure out they can take the opportunity without you, or the opportunity is only worth slightly more than $1 million per year, so it isn't worth their time to cut you loose (since you, in effect, will be getting a "finder's fee" for finding the opportunity for the team).