This is fantastic. Another method to "tricking yourself into being awesome" (also called learning) is to jump right in and start working on a project. Like the author, you'll come up with loads of questions that need answering, and if your project is going to be successful, those questions must be answered. Otherwise your project/startup will die.
Personal experience: this is exactly how I learned Ruby on Rails as a non-programmer. I had an idea for a project, so I tried reading books and tutorials for months. Nothing stuck. It just didn't make sense. I couldn't translate the words I was reading into code. So I said "screw it" and started hacking away at my project, with absolutely no idea what I was doing. Progress was slow obstacles were rampant, but it turns out those obstacles are easy to overcome with stack traces and google/stackoverflow!
Personal experience: this is exactly how I learned Ruby on Rails as a non-programmer. I had an idea for a project, so I tried reading books and tutorials for months. Nothing stuck. It just didn't make sense. I couldn't translate the words I was reading into code. So I said "screw it" and started hacking away at my project, with absolutely no idea what I was doing. Progress was slow obstacles were rampant, but it turns out those obstacles are easy to overcome with stack traces and google/stackoverflow!