* Alan Gauld via Tutor <tutor@python.org> [2016-05-30 22:11]: > On 30/05/16 06:45, Steve Lett wrote: > > write code., lots of it. > > Don't just settle for the examples/exercises in your book. > Use them as a start but extend them. Add extra features. > Change the output format or the sort order. > Combine examples to make bigger programs. > > Writing code means making mistakes and, in finding the solution, > you learn far more than from just reading code.
And a corollary to this: have a purpose for why you are writing it. Learning code for the sake of learning it will get old quickly. You will get a lot further if you are trying to solve a problem that you care about. Think of something you would like to automate, or calculate, or process. Do you have data you would like to analyze? As you learn different elements and apply them to a practical use that does something for you, it will be more satisfying and more likely to stick in your brain. -- David Rock da...@graniteweb.com _______________________________________________ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: https://mail.python.org/mailman/listinfo/tutor
