[raju]

I have been thinking about this for a while now, and I am not quite sure how to apply it, to say learning a new (programming) language (I have been playing with Clojure for a while now but am nowhere near productive in it).

I guess the part that confuses me is the first step - "R stands for Reaching/Repeating" - How exactly would you apply this to learning a new language, framework, algorithm?

Folks here on HN - Any words of advice?

[teach]

When I wanted to get better at Python, I started working through the problems at Project Euler[0], because they were novel and interesting. Also, many of them needed non-trivial optimizations to produce an answer in a reasonable amount of time.

After about 20-25 problems, I found myself reaching for the Python docs way less.

[0] http://projecteuler.net/

[bostonvaulter2]

Similar to what teach said you could apply some of it by trying to code without using the docs as much as possible. But I agree that it's hard to "practice" programming, versus "doing" programming.

So much of programming is working with large complex systems that it isn't that amenable to small drilling techniques.