Saturday, June 30, 2012

Ok, so the snake isn't so slimy afterall. Mod4

First off our instructor really went the extra mile with the lecture.  It was a full 156 minutes with two significant demo sessions.   Our lecture slides were full of good "do able" information.  If one compared the Exercises there was significant realistic get it accomplished information.  Let's give Theron a hugh Thanks!     

For this newbie at least some of it is beginning to make sense.   Truly it is comparable to learning a new language.  At least I'm not as lost as I was and can find the door better than the bear in Assignment 4c, that was a crazy insanity python loop joke, I think.   

Some tips of significance.
   a)  Save your work if you can. 
   b)  Print out windows of the Idle to learn how you did that cause many times, it gets lost in
          translation.   By doing the printout, I began to see my common typing mistakes which
          result in simple time eating syntax errors.    Also I began to see in print how to correct
         other more significant issues.

   c)  Type slower,  get a pair of better glasses.   The . and , look the same late at night but are
        not the same to the computer.
    d)  CaseSensitivity.  Ugh this program just can not suck it up and get along, it must have its
        way specifically.  A diva in disguise.
    e)  Looking help up on the internet can be a challenge. Learning what to call it that I'm not
         figuring out it a stretch.
    f)   Usually when I think I"m the only one, there is someone else out there who is also too
         embarrassed to ask because it seems so small an issue which is eating me alive (the snake
         has a big mouth).   
    g) I'm not a quitter, I'm determined and will eat anything alive to figure it out.  So, don't take
        anything personal, it's just the learning process here.  
   
Other tips with the program.
    1- Indentation, it matters.
    2- Case Sensitive , said this already.
    3- One tenny tiny thing will cause it not to "go"  in my language.
    4- Running one line at a time in a script is a good plan to catch mistakes, correct in the dual
        script window and correct at the same time.
    5- Naming files & scripts clearer than data to what it did or accomplished, easier to find later.
    6-Using a dual screen with pywin for scripts on one side and Idle on other for running line by
       line is a good combination.

  7-Entering text for a long passage is a absolute pain, there must be a better way.  Will find it soon.
  8- If, elif else are tricky.  Need indentation, can indent in the indent.  Are more like the old flow charts if yes go there, if no go here, but, there is always one.  They need a way out otherwise it becomes a crazy loop thing that keeps going.  Like the computer at the fair that must have had a plus 1 program that was up to 205,000,000 and going. 

 9- One always has to tell the program what something is for it to work.  Much like husbands, they are not able to read minds and the wives who think it in their head and do not get it out of their mouth to the husband who did not do it cause he did not know that he was suppose to because he did not get the memo that was not spoken by the wife who expected the husband to know what she wanted. 

No comments:

Post a Comment