Re: Python books __Jens__

[r j]

Jens yes I do need to block off some hacking only time. I have run all the code in Learning Python and half the code of programming Python through the interpreter. It does take time and I do not like to download the code for the book and run it.
 I type it all out.  As far as dirty hands outside of books just problem solving in programming logic in python. I will do extensive network programming in the months to come and plan on learning and coding my own solutions. I have lacked focus, and now I am focused on networking. /* Ron */

On Tue, Dec 15, 2009 at 10:18 PM, Jens Knutson <jens.k...@gmail.com> wrote:

Hi Ron,

Have you tried doing much actual hacking around the kind of Python networking code you're talking about?  It seems like you've probably read almost everything there is to read on the topic, reference-wise.

If you haven't tried out much actual code, block off an evening, lock yourself in your den/bedroom/basement, and just spend several hours just hacking away, playing with this stuff.  There's nothing like experience as a teacher!  Plus, it's *Python*, so even if the learning curve is steep, at least you'll have a pleasant journey. :-)

(Forgive me if I'm wrong in my presumptuous guess about how much you've gotten your hands dirty with this kind of code!  If that's the case, do you have anything interesting to relate around what you've tried and how it went?)

- Jens

-- "We act as though comfort and luxury were the chief requirements in life, when all we need to make us really happy is something to be enthusiastic about." - Charles Kingsley

[Dan Frankowski]

Ron,

Jens suggested "hacking away, playing with this stuff." My suggestion is don't type code from books. The most important part of learning is picking a task you actually want to do. Then you can try building the thing you want. All the books look completely different: they are now bags of code that you are reaching into to accomplish your goals.

Dan