This class should be two classes. CS 111 had the most readings of any course I've taken at UCLA, and the projects were very unforgiving. The only saving grace for this course was that the midterm and final were fairly manageable so long as you did the readings, but there's so much to cover that you'll likely lose points here-and-there depending on the strictness of the graders. Reiher is also a good professor so I recommend taking CS 111 with him if you can. Also, don't trick yourself into thinking that taking it over the summer can make it easier. This may be the case with other courses but for us we had project due dates packed so closely together that the 2nd to last project was due the day of the final exam and the last project was due less than a week later with a hard deadline.

tl;dr CS Major Beware, You're In For A Scare

Despite hearing he is easier than other professors teaching this course, I still found the workload to be a ridiculous amount. 100+ pages of dense OS reading every week, alongside large projects that have nothing to do with the lectures. It's like they are two different classes. Professor Reiher tried his best to squeeze a course designed for a semester system into our very own rubbish quarter system, and the students pay the price. It's like CS kids aren't allowed to do anything besides study lol

Reiher is definitely a lot easier than the other professors. You don't have to attend lectures as he reads straight off the powerpoint. There is a ridiculous amount of work though, 100 pages reading a week at least and a 10-20 hr project. Good luck.

You get to learn a lot of cool stuff about how a computer really works on a lower level in this class, and how the abstractions we use on a daily basis are constructed - which is what made this class really fun for me. With Reiher, you HAVE to know your content in and out because the tests really check if you understand each and every concept and you can't get away with just kinda knowing it. That said, Reiher is a great professor: he may not be the most engaging, but if you manage that - just keeping up with lectures and readings should be good for this class. Also, projects are a pain - get started on them as early as possible (they do get easier towards the end of the quarter though).

Reiher is one of UCLA's top notch professors. Always open to answering students' questions and gave engaging lectures with some humor thrown in here and there. Even though most of us won't go into OS development (or debugging for that matter), this class teaches you how computers work behind the scenes to make applications run smoothly together (e.g. resource sharing), how the most vital piece of systems software interacts with the hardware to create the abstractions us programmers often taken for granted, and most importantly develop a systems mindset for thinking about software. Projects were time consuming so please start as early as possible; tests are quite unpredictable tbh could be very detail oriented or require tying together general concepts. The only real way to prepare for his tests is to do the readings AND take notes of the key ideas. The difficulty of this class is over-hyped it is definitely manageable if you put in enough effort and time. From what I heard, Kampe is a bad lecturer and Eggert is Eggert so... better to take it with Reiher. If you're a HSSEAS student and plan on tech breadthing in CS, definitely take 111 as this is one of the core classes that distinguishes between a programmer and a software engineer.

Definitely take this class with Reiher. It's time consuming and the projects are hard, but that will be the case with any professor you have for this class.
There's a lot of reading so definitely do it each week as he assigns it. When the midterm and final comes along it's just way too much material to cram for.
Lectures are entirely slide based, so feel free to skip them and review it on your own. Lecture material closely parallels the assigned reading that week, but there are some topics in the lectures but not in the readings (and vice versa) that comes up on the tests so you absolutely need to go over both.
Projects are really difficult, the biggest help was my TA (Jonathan Lin, highly recommend) during discussion section and office hours. I would go around and check out each TA, some explain things better but others have sample code which is super helpful.
Reihers late policy is similar to Eggerts but a little harsher (something like 2^(n+2) iirc) so there's some wiggle room, but keep in mind you have a project due every week so it's best not to fall too far behind.
The tests are the biggest reason to take this class with Reiher. The midterm and final both consist of writing answers of around 5 sentences for questions like "What is password salting" or "What scheduling algorithm best prioritizes _?" Some might be tougher but in any case, reviewing reading and lecture notes can definitely get you a solid grade on the exam. It's much easier and helps you learn the material more.

This class is not very hard, but there is a good amount of work you must put into it. Professor Reiher uses slides and reiterates with more clarity, but many people skip his 8 am lectures and instead go through his posted slides on their own. Midterm was 10 short answer questions while the final was 15, and both tests were very fair. The TAs go over the projects in discussion, and fortunately for me, I had very good TAs who went over the project specs in-depth. Though, some of my friends had a TA who wasn't very helpful, so I would switch ASAP to a better one if possible as it really cuts down your project time. Overall, your grade reflects the amount of effort you put into it. I'm not the smartest CS student, but I still managed to pull off a good grade. As long as you keep up with your readings (which many students don't), you should be good to go. This class has many important concepts, so you might as well put lots of attention to it.

CS111 requires tons of work. Reiher's tests are reasonable. If you spend enough time to study, it is manageable to get a good grade.

Professor Reiher is one of the most valuable professor in the CS department. I took both 111 and 118 with him, and even though from time to time the lectures could be a bit slow, his method of teaching these class adds valuable knowledge to your repository.

He mainly uses slides and explains them during lectures. Many people find this kind of boring which is understandable. If he could reduce the details a bit and use the blackboard from time to time it would be fantastic.

Like other people said, projects are entirely handled by TAs which is both good and bad. If you have a TA who is lost and really doesn't know their stuff, then good luck! Otherwise, you should be fine.

There was one midterm and one final. Midterm focused on details and concepts of OS and networking(in 118) and the final is about using those concepts to design something efficient that works. You might find it unconventional, but in my case that was actually very practical.

Overall, a very good professor and I recommend him.

Reiher relies 100% on his slides. His lectures can be boring, but he moves through material quickly and in depth. Reiher has no involvement with the projects at all, they are completely assigned, handled and graded by the TAs. The projects can be very time consuming, so it's important to work closely with your partner and go to office hours if you are unclear on implementation details.

Reiher's version of this class requires a lot of memorization of fine OS details, alongside fairly deep understanding required to pull concepts together to answer the long-form test questions. Open note final does help but the final is also brutal.