> But the reason I ask this, is because there are SO many different approaches
> you could
> take to a single problem,
I guess that depends a lot on what sorts of problems you are thinking in terms
of. At least in many cases, perhaps one of the points of the Zen of Python is
useful:
"There should be one--and preferably only one--obvious way to do it."
I myself have been trying to stick to that for now; to learn some standard ways
to do certain things, to not reinvent the wheel but instead to use the standard
library and modules to do what I need done (since someone already needed it
done before and coded it well then). Yes, gaining more flexibility in how
you could approach something is also good, but for learning I have tried to
establish a core of basic approaches first, and alternate approaches second. I
feel that if it works, it's readable, simple, and re-usable, I put it in the
toolbox.
> how do you know which is correct or why one is better than the
> other? You can dig yourself in to holes with more complex problems, and not
> understand
> why.
This list is one good resource for comparing notes on "correctness" of
approach. You'll see people ask if something is "Pythonic" or not, etc.
_________________________________________________________________
Windows 7: Unclutter your desktop. Learn more.
http://www.microsoft.com/windows/windows-7/videos-tours.aspx?h=7sec&slideid=1&media=aero-shake-7second&listid=1&stop=1&ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL_WIN_7secdemo:122009_______________________________________________
Tutor maillist - Tutor@python.org
To unsubscribe or change subscription options:
http://mail.python.org/mailman/listinfo/tutor
