Hi jim,
I make lists of steps all the time.
It is pretty much an algorithm, but in some cases, I am not really sure of
what the right steps are yet.
Sometimes at that point, I try doing a little research, to
To see what other people have done and what is known about the problem
already.
On some math-related problems, I have consulted wikipedia and gotten some
insights, formulas,
and ideas from their articles.
Also, the more Python you know about, the more tools you have to work with,
and Python tools can save you some headaches in quite a few cases.
Don't take all your time to learn stuff before you write anything.
Just schedule some time learning new stuff while you're doing your coding on
existing projects.
Sometimes it is hard to keep all the balls juggling in the air at the same
time.
If you are stuck or having trouble working out a problem,
that's what the email list is for.
We can give you some hints on how we would approach the problem,
or what we think you are trying to do that might not work very well.
I think feedback from others is always very useful,
and generally, I regret not asking and getting more of it when I might have.
I'm always happy to receive all your discussions and thoughts on what and
how you are thinking about programming and your program challenges.
In general, I am still trying to get the hang, and habit, of using
classes.
Sometimes, it is rather hard to see in advance, exactly how the classes for
a project should be formed,
i.e. split into groups of data and methods that are closely interrelated.
The problem is when you get a "new" piece of data that doesn't fit into your
developing class structure,
but that bridges across multiple classes,
and just doesn't seem to work with the rest of the layout,
and you have to start over from scratch, and aren't sure for awhile,
what the right answer is, because all your previous thinking is somehow
flawed.
Then it could be time to consult with a friend or post to this email list
for some advice before you entirely give up in frustration.
My knee-jerk initial reaction to dealing with any programming problem, is to
come up with a set of functions, procedurally,
for solving any particular problem.
Sometimes, I find myself going back, and rewriting the code to be done with
classes,
which is not the best way to do things.
We all have a lot to learn.
Jeff Thompson
------
-----Original Message-----
From: pythonvis-bounce@xxxxxxxxxxxxx <pythonvis-bounce@xxxxxxxxxxxxx> On
Behalf Of jhomme1028@xxxxxxxxx
Sent: Wednesday, July 22, 2020 4:59 AM
To: pythonvis@xxxxxxxxxxxxx
Subject: [pythonvis] A Classic Mistake
Hi,
You would think I would have not done this after having a programming
background. I figured out how I was unable to get the next Farkle project
post out on Sunday. I tried to code before I planned. Closely related to
that, I tried to force a lesson to fit what I was trying to code, when it
may not have been the best solution, and probably was not. So this time I'm
going to write out in English words what I want the code to do, then code it
in Python, then put out the post.
This leads me to ask you this question. How do you plan your projects?
If I do it correctly and write down what I want the code to do, it seems
that the code almost writes itself. Usually after that, though, the code is
different than the plan. That's OK, though, because the plan, together with
me trying to work out the plan in code, is way less frustrating and I learn
more. I usually do not go back and re-write my plan after I code, though.
Maybe I should do that.
What's that quote about executing a bad plan is better than not planning?
Hmm.
Thanks.
Jim
==========
Jim Homme
Skype: jim.homme
FreeChess: jhomme
Twitter: jimhomme
Facebook: jimhomme
Website: jimhomme.com
List web page is
//www.freelists.org/webpage/pythonvis
To unsubscribe, send email to
pythonvis-request@xxxxxxxxxxxxx with "unsubscribe" in the Subject field.
List web page is
//www.freelists.org/webpage/pythonvis
To unsubscribe, send email to
pythonvis-request@xxxxxxxxxxxxx with "unsubscribe" in the Subject field.
