3. Programming Tips and Study Skills#

a little bit of metacognition

For more on debugging, julia evans is a professional devleoper and the author of wizard zines

3.1. How did yesterday’s homework relate to today’s class?#

  1. the preview: we used groupby and I explained it some, but in less detail, more through example than the reading

  2. calculating percentages: the homework had you review something I thought you should know from high school, but it maybe was not fresh in your mind. Doing it in the homework made it fresh for all of you.

3.2. Student Generated Tips#

The following are all of the ones that students put together in the list:

3.2.1. Group 1 - 1pm#

  • there’s more than one way to solve a problem

  • add comments to understand what your code is doing

  • Learning how to code different kinds of graphs

  • Having to actully think and problem solve

  • Being able to solve the same problem in different ways

3.2.2. Group 2 - 1pm#

  • run every code first before adding more into the bar (to make sure it is working properly, and if its not you can fix why the code isnt working rather than fixing the whole entire code from scratch)

  • Looking at the type of error to figure out what mistake you made.

  • There’s a certain tool that can help you figure out the code if you ever forget it.

  • Studying in college is way more important you cant bullshit like last year.

3.2.3. Group 3 - 1pm#

  • Seeing how coding works, getting a feel for how it will be in the fall.

  • Writing notes in between your code is very helpful

  • looking at the last line when getting a syntax error can be very helpful

3.2.4. Group 4 - 1pm#

  • Syntax/formatting is very detailed.

  • Make a list of key words

  • previewing and preapring for lecture

  • Take your coding piece by piece.

  • Practice independently

  • How to make headers for our titles

  • Read over notes and explain the notes

  • How to read python scripts

  • The difference between code and markdown.

  • Commenting in your code.

  • Work with peers.

  • Using the help provided with the IDE.

3.2.5. Group 5 - 1pm#

  • General keyboard shortcuts

  • Break codes down to pieces then re-plugging to make it shorter and be able to obtain the help menu

  • Debugging until you see the mistake then go back and fix it.

  • The precise logic that’s needed in terms of making the code run, but ways to read said logic and break it down

  • The importance of previewing

3.2.6. Group 1 - 3pm#

  • Preview the class materiel before class.

  • Go to office hours.

  • Use the tool for when you are stuck with coding.

3.2.7. Group 2 - 3pm#

  • getting error codes on incorrect codes so you can learn from your mistakes and being able to read the error on your message.

  • preview and using what you might of seen in the preview in the next lesson

  • skimming through articles finding what the teacher mainly wants you to look for

3.2.8. Group 3 - 3pm#

  • Break down tasks into smaller chunks

  • Previewing before class

  • Note taking

3.2.9. Group 4 - 3pm#

  • Previewing the information before class

  • Reviewing what was leanred form the previous class and applying it to new material

  • self testing codes that was learned in class

4. Group 5 - 3pm#

  • Previewing material before class

  • Shift + Tab help menu

  • Going through things slowly to make sure your code is corrrect instead of running all the code at once

  • Take advantage of office hours

  • Ask questions in class

4.1. Group 6 - 3pm#

  • Previewing prior to class

  • Reviewing after class

  • Shift + Tab help menu

  • Making sure you read through things slowly

  • Using shift tab in between parentheses for when you need help

  • Ask questions in class

4.2. Summary - Top Tips#

Warning

TBA