Do what this guy did: http://news.ycombinator.com/item?id=438646 http://news.ycombinator.com/item?id=438646 I'm always most successful at getting something don

Do what this guy did: http://news.ycombinator.com/item?id=438646 http://news.ycombinator.com/item?id=438646 I'm always most successful at getting something done when I: choose the smallest useful thing I can think of, choose something even smaller instead (which can be expanded later), develop a schedule for getting it done (e.g. 1 hour per day), keep a calendar showing whether or not I'm working as hard as I said I would (no slacking!) and timebox the whole thing (lack of time is the greatest motivator in the universe). Update: for fun, I actually just tested this. I tried to write a language interpreter in Arc that could execute the following function: (def fib (n) (nth n (sequence s 0 1 (+ s.-1 s.-2)))) which is written in a hypothetical Arc-like language I just invented. I gave myself 30 minutes. I didn't get it done, but I did pretty well. The language had a namespace, functions, macros and all the basic operators I needed. Unfortunately, I didn't quite finish the eval function. Another 10 minutes and I would have had something I could run (although I don't know how long it would have taken to fix all the bugs).