Exam practice/prep

[wence-]

Are there specific resources apart from lectures/practicals and exam papers will be useful for me to practice for the exam?

[wence-]

I think there are two parts to this:

1. The practical aspect of being comfortable programming in Haskell. For this the practicals are probably sufficient. You may wish to revisit some of the earlier practicals having become more familiar with Haskell and try writing more succinct answers (perhaps using the higher-order functions and ideas we saw later in the course). Naturally, these are quite small and tailored to particular examples. If you want to try larger problems to practice Haskell (and the translation of specifications into code) you could do worse than attempting some of the Imperial "January Haskell tests". I also like the programming challenges at adventofcode (they are well-specified and start out quite straightforward, although you may find the constant references to Santa a bit tedious at this time of year). The typical exam questions that ask for Haskell code are not this long (don't worry!).
2. The more holistic aspect. This course is on programming paradigms as a whole, so questions may also ask you to compare and contrast different approaches to the same problem. I tried to cover some of these in my running commentary of the code I was writing, and have added links to interesting articles in my "summaries" of the lectures. So reading some of these things and trying to understand the arguments they are making will be useful. I would advocate that thinking about types and understanding the different type-based patterns for writing correct and maintainable code are more broadly applicable than just attempting to pass an exam, so I encourage you do it in general.

I guess a shorter way of saying those points is to practice programming, but at the same time, think about not just the details of how you're solving a particular problem, but whether there are any underlying abstract patterns or structure that you can exploit for generalisation. This latter need not always be in Haskell: one can critically appraise object-oriented code from the point of view of a functional programmer.