The Prolog issue hilariously still hasn't been fixed. They're using the same lectures they used I believe 2 years ago. So to be very honest, it feels like on that front very little effort is being put into. However, just because it isn't high effort doesn't mean it's not an enjoyable and generally well-written subject. Aside from the jarring Prolog Haskell module issue that I doubt they'll even fix any time soon, the modules are quite well-written, compact and easy to grasp. The lecture slides pretty much provide you with the 'skeleton' knowledge of what you need to know, and along with the recordings, I think you won't have too much of a problem understanding the concepts. Of course, the lecturer does at times glance over things even when things get a bit abstract, so you might need outside help such as Youtube (though that's completely normal for CompSci). I think what really sells is the Ed discussion board. The tutors, particularly James, are incredibly helpful and are often always ready to answer any question. So, the learning process is made much easier thanks to their help, which I honestly appreciate a lot. Overall, just a fun and very interesting paradigm to get your hands on to. I think it's worth taking if you're majoring in Computing and Software Systems. One might say Prolog is a bit too academic to be practical, but I think same argument cannot be applied to Haskell. And the paradigm itself, abstractly, is widely implemented in a lot of other languages such as Rust and Go. So, studying it in-depth like this may prove useful for a lot of CompSci students. Had they fixed the Prolog modules (which would not have made a few things concerning Prolog towards its end so disorienting), this would've been an easy 5-star.

Would be 5 if it didn't have the problems the user stated below. Hopefully next time its ran the problems will be fixed because they seemed to be transitional problems. It was poor that this happened, but the subject is still great, especially if you are more of a CS nerd and like pure programming and problem solving.

Don't take this subject. in Sem2 2020, they moved around the course so that the second half of the course (prolog) is moved before the first half (haskell). Normally this won't be an issue, but they literally just copy pasted the content. This meant that we began with hard abstract recursive content, which we self taught. And then in the middle of the course, we started learning introductory content.... which we had already taught ourselves. No effort was made to change the materials, slides were just copy pasted. The LMS dates for assignments were still from last semester until week 9. The projects were arbitrary and dull. The language prolog being learned is outdated and very niche. The instructor made 0 effort in making things interesting. It was code on slides, and 3 paragraphs of text explaining it, and in lectures he would just read over them. I would avoid this, teach yourself haskell and functional programming outside this subject. A pretty bad experience overall.

I would avoid this subject if you're an average student. The concepts are very abstract and nothing like other programming languages. Plus it's not really of any use in almost every context you could think of.

It is one of the most fun subjects but a little bit challenging as well. That's because declarative programming languages (Haskell and Prolog) are different from your daily using imperative languages (Java, Python, C, C++). The teacher creates project tasks, and you can't find anything similar, so you have to be creative as well to solve them. Don't leave them until the last day - probably you can't complete them in time. Exams are very similar to the tutorials, so if you can solve them, there is no reason to worry.