CS131 is a HARD class but Carey is probably the best one out there to teach it. We had 10% homeworks graded on effort, 30% projects (3 projects 10% each), 25% midterm, 35% final. The projects were extremely brutal, by brutal I mean spending more than 30 hours on each project, pulling your hair out and trying to find test cases that would break your code (getting edge cases). The projects build on each other and we basically build our own Interpreter (Brewin) using Python. The first project was the hardest because we had barely any skeleton code but the projects got progressively easier as he released his solutions for project 1 and project 2 for you to build on after the due date. The exams were difficult but not too crazy, the average of the midterm was about 65% ish and the final was about 70% ish. I would say just prepare yourself to spend a lot of time on this class, probably the most you would ever spend on a class. Take this class with easier classes so that you can dedicate the time to the enormous amount of content that this class has. It is very content heavy and extremely time consuming. On the bright side, this is only the second edition of Careys version of the class and it can only get better from here. All the best!

If you have to take CS131, definitely take it with Carey. This was the first quarter he taught it, so some imperfections were expected. Overall, Carey and the TAs (pre-strike) were all very passionate and helpful. They actively listened to our feedback and put in a lot of effort to improve the class.

Class website: https://ucla-cs-131.github.io/fall-22/

The homework (graded on completion) was initially very long, but they listened to feedback and made some questions optional. The projects were a bit more time-consuming than initially expected (maybe 20+ hours), but the autograder was insanely helpful to instantly see your score on Gradescope, and there was a subset of the test cases publically available. The exams (open book) were fair but challenging, and really tested your deep understanding of the concepts. The course material wasn't particularly difficult, but there was a significant amount.

Advice: (seriously) don't procrastinate on the projects! Try to keep up with the course content because it's really easy to fall behind. Attend lectures (he's entertaining and gives out snacks) - it may feel easy to ditch because he posts his slides, but he will explain things more clearly than if you skimmed through the slides yourself.

Had a great time with him. Lectures are very clear but move quickly as there is a lot of material to cover. The exams are close to what we cover in lectures but more difficult. But it's still good, at least the professor covers a lot and won't let you see the questions and have no idea what to do like Eggert's exam.

Very well organized class. F22 had three projects (which build on each-other) where you had to build an interpreter for a new language. Pretty heavy workload for these, but grading was transparent (through a Gradescope autograder). Carey's a good lecturer, as usual. Exams were pretty tough IMO, and the class ended with about 30% A's, 30% B's, and 30% C-F's. Best strategies would be to have the concepts down perfectly and get a lot of practice programming in the languages that you study that quarter (for us it was Haskell, Python, and Lisp.)