1 / 8

Learning to program

Learning to program effectively involves active engagement through writing, reading, and receiving feedback on code. This journey emphasizes hands-on experience by crafting your programs and examining others' work. Techniques like peer evaluations and pair programming enhance learning outcomes, allowing students to share insights and suggest improvements. By collaborating closely, participants can tackle challenges together, ensuring a deeper understanding of programming structures. Utilize provided resources and worksheets during in-class sessions to solidify your skills and help fellow learners.

chad
Télécharger la présentation

Learning to program

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Learning to program

  2. Learning to program • One learns to program by doing. • Writing your own programs • Reading others programs • Studying good programs written by others • Getting lots of feedback about your own programs

  3. Peer Evaluation • You can’t learn to program unless you write programs. • You learn to write better programs by getting feedback. • I can’t give enough feedback to a class of any large size. • Peer evaluation is utilizing students to provide feedback to other students about their programs. • This is serious business • Both the program author and the peer evaluator can learn a lot from this practice.

  4. Pair programming • Work in pairs. • Two sets of eyes and brains is better than one. • One person “drives” – works the keyboard. • One person “navigates” – decides strategy and looks for errors. • Switch roles at least every half hour. • Think before you type!

  5. Code walk throughs • The author of a program explains his code line by line to a group evaluators. • The evaluators • ask questions about what they don’t understand • Suggest improvements to code • Suggest code restructuring • Code structure (use of abstractions, functions, modules etc), comments, indentation are all subject to suggesstion.

  6. The programming resource link

  7. In class programming worksheets • We will often use worksheets in class • Go to the programming resource link page • Download the worksheet to your own computer • Work in pairs to complete the worksheet. • When your pair is finished. Get up from your table and find a pair that could use some assistance. • Over their shoulder (don’t touch the computer!) help them to finish the worksheet • When everyone is standing we’ll move on to the next unit.

  8. Using resources • Study the resources provided. • Try and recognize what makes a program good. • Learn the “structure” of programs. Many errors are silly misspellings or forgotten punctuation. • Always ask for help! Many times another pair of eyes will immediately see what’s wrong.

More Related