[Tutor] Fwd: Re: Learning to program, not code. [LONG RESPONSE!]

[boB Stepp]

It appears that Michael only sent this to me when I think he meant to send
it to the list...

---------- Forwarded message ----------
From: "Michael Shiloh" <michaelshiloh1010 at gmail.com>
Date: Dec 21, 2014 7:25 PM
Subject: Re: [Tutor] Learning to program, not code. [LONG RESPONSE!]
To: "boB Stepp" <robertvstepp at gmail.com>
Cc:

> On Fri, Dec 19, 2014 at 08:12:14PM -0600, boB Stepp wrote:
> > On Thu, Dec 18, 2014 at 8:09 PM, Brandon Dorsey <brandontdr at gmail.com>
wrote:
> > >
> > > Hello All,
> > >
> > > simple fact that I've been learning python for 8 months, and I have
yet to
> > > start, and finish, a simpleproject.  I find difficult to not only
visualize
> > > the execution, but to figure out when and where to
> > > use data structure 'x'.    Any suggestions on how to approach
programming
> > > from a different angle?
> >
> > I am going to take a stab at this. Perhaps the perspective from a
> > non-professional in the world of computer programming might be of
> > help.
>
> Very interesting question,  Brandon, and many excellent answers. I like
the
> comments that Bob made in particular.
>
> I have two modest suggestions:
>
> 1) Pretend you are explaining to someone else how to solve the problem (a
pet
> or stuffed animal would work as well). Pretend the person you're telling
knows
> very little so that you have to explain in great detail. I find this helps
> sometimes, but not always.
>
> 2) Bob made the wonderful suggestion that if the entire problem seems
> overwhelming, but you can see how to work on some small part of it, start
with
> that. I would add that if some small part of it interests you in
particular,
> start with that first. If you are excited or motivated, that will help you
> push through the bumps in the road.
>
> I often do the part I'm most curious about first.
>
>
> Good luck,
> Michael