Follow the following tips for the next exam:
Become more familiar and grow more confident with Haskell
Review mostly in Python and refer to Java equivalents for clarification.
Skim/re-read all reading assignments including textbook excerpts
Take notes over required readings – summaries and important lists only
Compose “cheat-sheet” in the same manner as the one for the first exam.
Begin studying a week to two and a half weeks prior. Light studying over the course of a week as opposed to intense “cram” studying two to three nights before-hand. Include practice examples. Maybe find a study partner.
Utilize Piazza in order to ask clarifying questions.
Actually code the examples on Github and play around with syntax.
I thought that the test on friday was very fair, and paced very well. I finished the last question right as time was called. That being said, I know that I could have done better. With a week crammed with projects and other exams, it was difficult finding time to study for the exam, but that is just an excuse. I should have looked at my calender more closely and made the decision to start studying the previous week. With a class like this, you are being tested over syntax and intricacies of the different coding languages. In other terms, as with most other CS test, it was a skills test. As with any other skill, you get better with practice and for this test, I did not practice nearly enough. I know that if I follow at least half of the suggestions listed above, I will do better on the next exam.
Paired Programming – Unsurprisingly, it went very well. I found that I was more on top of the assignment with a partner to work with. When I code by myself, it is very easy to procrastinate up until the date the assignment is due. Scheduling times that I would have to be focused on the assignment was very beneficial. I would say that by working on the assignment in chunks with a partner spread out over the two weeks helped in easing my stress.
Until next week. Rock 'n Roll
No comments:
Post a Comment