I have to say, I am slightly surprised at how much I enjoy reviewing code, both for the purposes of looking for small typo which cause bugs, and just to try and figure out what everything is actually doing. I’ve been working on Exercise 47 for the last few days and simply could not figure out what was wrong (I kept getting NameError: global name ‘self’ is not defined). I finally went back and looked at every bit of code that I’d written and finally found two tiny misspellings that I had apparently missed the other half dozen times I looked at it. And poof! It works!! Is there anything more fulfilling than finally having code run properly an spit out what you are expecting/hoping for rather than an error message?
In related news, I know I’m not quite all the way through “How to Learn Python the Hard Way” yet (I *AM* 90% done though!! xD), but I have started re-reading the first couple lessons in the Python GTK+ 3 Tutorial, and its making a lot more sense now 🙂 I know, you all told me not to do it till I was totally done, but what can I say? I’m impatient :p
Todo en Tiempo 
March 14, 2012 at 1:18 am
Woohoo! Way to go! You need to setup gedt or gvim so that you can catch those typos easiliy. Catch me on IRC, and I can point you to some documentation.
March 14, 2012 at 2:04 am
Python is the best language for learning both programming itself, and to learn how to structure and organize new programs you’ve never tried writing before. I love how well it abstracts the nitty-gritty stuff and how easily you can focus on the concepts of your code.
If it weren’t for Python, I probably never would have thought of programming. Learning to make something like that sort of changes the way you think- I’m sure you’ve noticed now that it’s clicking 🙂
March 14, 2012 at 3:02 am
may i have a link to the “Python GTK+ 3 Tutorial” you mention above pls? 😀
March 14, 2012 at 5:19 am
http://python-gtk-3-tutorial.readthedocs.org/en/latest/index.html 🙂