- Home
- Search
- Paul R Eggert
- All Reviews

Paul Eggert
AD
Based on 357 Users
If you do not have a background in the technologies that are supposed to be taught in this class, you will struggle. However, if you do, Eggert's lectures will teach you a lot about the broader concepts behind them.
Homework is not that bad and were graded fairly generously.
Tests are Eggert Tests so they tend to be pretty tough.
The project required a lot of outside work.
The projects are moderately hard. The midterm and final are ridiculously hard. Open book and open notes will help you little. If you want your effort to be paid off reasonably, avoid him at all costs.
Leave now!!
Wrote with blood and tear.
Unless you feel like you are smarter than 99% of your classmates.
Exams are more of creative writing questions rather than coding questions. One example question would be like "If you were to redesign system A on top of framework B, what's the pros and cons", at which point you can only freestyle write if you don't have the pros and cons of each system in your notes. Midterm had a mean and median around 63/100, final had a mean and median around 70/100, and yet still no curves on the final grades. I got 1 point above the average for midterm and about 82/100 for the final and got a B+. The whole class is appalled that no curves were given to such a low grade distribution. One TA said that past GPA distribution is around 2.7 for this class. It's pretty accurate. Don't be misled by the beautiful grade distribution of 2020 spring on Bruinwalk
I'll preface this by saying that I'm a mediocre CS student who scheduled his quarter to very generously accommodate this class' reputation as a hard class with a hard professor. I came in wanting to really learn this well, and I'm sitting at week 9 with an almost guaranteed drop (just waiting on my MT2 score) and feeling like I learned nothing of use.
Eggert is a brilliant man. He's a good speaker too, and manages to make the dry topic of assembly code and low-level computer architecture interesting. That being said, this class is one of my biggest regrets at UCLA. The expectations are unreasonable and the class is organized pretty horribly. He expects students to read the entirety of the over 1000-page textbook, and lectures are incredibly difficult to understand without it. They're pretty hard to understand even with the readings.
The homeworks and labs honestly shouldn't be incredibly hard. The problem is they're filled with bugs and issues. Instead of giving you the files that you need and then having you work through the assembly code, he gives you files that you need to configure, unzip from tarball, patch, or otherwise modify, often inside the linux servers, which he assumes you are completely fluent in using. This wouldn't be a big issue if they could just tell you what to do and why you're doing it, but the spec instructions are always incomplete. Ask the same question on piazza 7 times and you'll get 7 different answers, so your best bet is sitting in TA office hours for countless hours until your assignments are configured properly. If your TAs don't constantly decide to move their office hours, sometimes cancelling or moving them on piazza only after a student posts that they went to office hours and no one was there. But I felt like I was so bogged down in the trivial garbage of setting things up properly that I couldn't properly learn. Giving more assignments but cutting out the setup or giving Smallberg-style detailed instructions instead of a 1-page spec with 1000 missing steps would help tremendously with the learning in this class.
Late policy is generous, being 2^(n-1) percent loss for n days late. But because so many students get high scores on the labs (often through cheating, which even the TAs almost encourage, or through crowding office hours, which makes it impossible to get your questions answered), you can't afford to lose that many points on labs at all. Start early, because every step of every assignment will have unreasonable and unexpected errors... even if you use online solutions.
Tests are literally the most depressing thing you'll ever experience. Eggert makes his tests on the fly. They're good tests for the A students, but if you're not an A student, it'll leave you feeling hopeless. They're tangentially related to the course content but I definitely felt tremendously underprepared for them. Review sessions and discussions seemed to reinforce the material, but nothing could save me from the tests (even actually knowing the material, which I did on occasion). Maybe if you're good at BSing you can get on top of the curve. But if not, you're in for a rough time.
Overall, I thought the course was a pretty terrible experience. I learned quite little, was overwhelmed almost all the time, ran into 10000 bugs every time I tried to turn something in, and didn't get enough of a chance to apply the content to assignments. I have a lot of respect for Eggert's brilliance, but if you want a good learning experience and your sanity, take it with anyone else.
宝儿作为在职的软件工程师 讲他做喜欢的软件工程(不是计算机科学)
看得出来满腔热情
思路很快 得保持全神贯注
能学到很多
Honestly after taking 35L and 111 with Eggert I thought it couldn't get any worse but it does. This is hands down the most useless class I've ever been apart of. The amount of work involved with it is absolutely insane(much more than his 111 IMO), and his "late policy" is just his way of assigning more work than can be done in class.
For the Prolog section, he started going over the language the day the homework was due. Python project is due in less than 48 hours and he hasn't spoken about Python of TCP once haha. It's absolute madness. They need to rework this entire class. Remove one of the OCAML homeworks and maybe you could have a decent schedule.
Overall this class was definitely very useful towards learning about various aspects of computer science in terms of software development. Eggert was very engaging and the class wasn't as bad as I had initially thought (though the class was probably revamped and being a Sophomore helped as I had previous knowledge before coming in). Eggert is an amazing lecturer and the TAs were nice as well. The assignments were a bit difficult so they definitely took a lot of time to complete. For tests there is a wide variety of subjects tested on so it benefits to really understand how higher level concepts work as well as how to program in the ways taught during lecture.
This class is way too easy. We typically spend less than 1 hour per week on projects, and attending the lecture is somewhat optional. I just hope the exams can become harder to keep us understanding this course well. Eggert's class usually great and recommend this class for gpa boosters. 5/5
Screw this dude. Screws us over with ridiculous projects and insane exams that are so hard to answer because he gets philosophical in his questions. He delves into a lot of redundant history and just generally goes on long tangents for extended periods of time, makes him seem like a good professor who wants to make students learn in depth but also makes me question what the point of some of his lectures is when they never make the exam. And after all this shithousery, he doesn't even curve our final grades. I ended up with a C despite being a consistently A/A- student because I did dogshit on his exams. He may have helped amplify my passion for CS, but I'm never taking another class with him again. My GPA and mental wellbeing took a strong hit with this dude.
TLDR - If you care a lot about cs at the risk of your own sanity/free time/grades, by all means ignore this review. If you just want to learn stuff and do exams and do a project, be very careful about this man and this class. It will screw you over if you're not at the very top of your game.
If you do not have a background in the technologies that are supposed to be taught in this class, you will struggle. However, if you do, Eggert's lectures will teach you a lot about the broader concepts behind them.
Homework is not that bad and were graded fairly generously.
Tests are Eggert Tests so they tend to be pretty tough.
The project required a lot of outside work.
The projects are moderately hard. The midterm and final are ridiculously hard. Open book and open notes will help you little. If you want your effort to be paid off reasonably, avoid him at all costs.
Exams are more of creative writing questions rather than coding questions. One example question would be like "If you were to redesign system A on top of framework B, what's the pros and cons", at which point you can only freestyle write if you don't have the pros and cons of each system in your notes. Midterm had a mean and median around 63/100, final had a mean and median around 70/100, and yet still no curves on the final grades. I got 1 point above the average for midterm and about 82/100 for the final and got a B+. The whole class is appalled that no curves were given to such a low grade distribution. One TA said that past GPA distribution is around 2.7 for this class. It's pretty accurate. Don't be misled by the beautiful grade distribution of 2020 spring on Bruinwalk
I'll preface this by saying that I'm a mediocre CS student who scheduled his quarter to very generously accommodate this class' reputation as a hard class with a hard professor. I came in wanting to really learn this well, and I'm sitting at week 9 with an almost guaranteed drop (just waiting on my MT2 score) and feeling like I learned nothing of use.
Eggert is a brilliant man. He's a good speaker too, and manages to make the dry topic of assembly code and low-level computer architecture interesting. That being said, this class is one of my biggest regrets at UCLA. The expectations are unreasonable and the class is organized pretty horribly. He expects students to read the entirety of the over 1000-page textbook, and lectures are incredibly difficult to understand without it. They're pretty hard to understand even with the readings.
The homeworks and labs honestly shouldn't be incredibly hard. The problem is they're filled with bugs and issues. Instead of giving you the files that you need and then having you work through the assembly code, he gives you files that you need to configure, unzip from tarball, patch, or otherwise modify, often inside the linux servers, which he assumes you are completely fluent in using. This wouldn't be a big issue if they could just tell you what to do and why you're doing it, but the spec instructions are always incomplete. Ask the same question on piazza 7 times and you'll get 7 different answers, so your best bet is sitting in TA office hours for countless hours until your assignments are configured properly. If your TAs don't constantly decide to move their office hours, sometimes cancelling or moving them on piazza only after a student posts that they went to office hours and no one was there. But I felt like I was so bogged down in the trivial garbage of setting things up properly that I couldn't properly learn. Giving more assignments but cutting out the setup or giving Smallberg-style detailed instructions instead of a 1-page spec with 1000 missing steps would help tremendously with the learning in this class.
Late policy is generous, being 2^(n-1) percent loss for n days late. But because so many students get high scores on the labs (often through cheating, which even the TAs almost encourage, or through crowding office hours, which makes it impossible to get your questions answered), you can't afford to lose that many points on labs at all. Start early, because every step of every assignment will have unreasonable and unexpected errors... even if you use online solutions.
Tests are literally the most depressing thing you'll ever experience. Eggert makes his tests on the fly. They're good tests for the A students, but if you're not an A student, it'll leave you feeling hopeless. They're tangentially related to the course content but I definitely felt tremendously underprepared for them. Review sessions and discussions seemed to reinforce the material, but nothing could save me from the tests (even actually knowing the material, which I did on occasion). Maybe if you're good at BSing you can get on top of the curve. But if not, you're in for a rough time.
Overall, I thought the course was a pretty terrible experience. I learned quite little, was overwhelmed almost all the time, ran into 10000 bugs every time I tried to turn something in, and didn't get enough of a chance to apply the content to assignments. I have a lot of respect for Eggert's brilliance, but if you want a good learning experience and your sanity, take it with anyone else.
Honestly after taking 35L and 111 with Eggert I thought it couldn't get any worse but it does. This is hands down the most useless class I've ever been apart of. The amount of work involved with it is absolutely insane(much more than his 111 IMO), and his "late policy" is just his way of assigning more work than can be done in class.
For the Prolog section, he started going over the language the day the homework was due. Python project is due in less than 48 hours and he hasn't spoken about Python of TCP once haha. It's absolute madness. They need to rework this entire class. Remove one of the OCAML homeworks and maybe you could have a decent schedule.
Overall this class was definitely very useful towards learning about various aspects of computer science in terms of software development. Eggert was very engaging and the class wasn't as bad as I had initially thought (though the class was probably revamped and being a Sophomore helped as I had previous knowledge before coming in). Eggert is an amazing lecturer and the TAs were nice as well. The assignments were a bit difficult so they definitely took a lot of time to complete. For tests there is a wide variety of subjects tested on so it benefits to really understand how higher level concepts work as well as how to program in the ways taught during lecture.
This class is way too easy. We typically spend less than 1 hour per week on projects, and attending the lecture is somewhat optional. I just hope the exams can become harder to keep us understanding this course well. Eggert's class usually great and recommend this class for gpa boosters. 5/5
Screw this dude. Screws us over with ridiculous projects and insane exams that are so hard to answer because he gets philosophical in his questions. He delves into a lot of redundant history and just generally goes on long tangents for extended periods of time, makes him seem like a good professor who wants to make students learn in depth but also makes me question what the point of some of his lectures is when they never make the exam. And after all this shithousery, he doesn't even curve our final grades. I ended up with a C despite being a consistently A/A- student because I did dogshit on his exams. He may have helped amplify my passion for CS, but I'm never taking another class with him again. My GPA and mental wellbeing took a strong hit with this dude.
TLDR - If you care a lot about cs at the risk of your own sanity/free time/grades, by all means ignore this review. If you just want to learn stuff and do exams and do a project, be very careful about this man and this class. It will screw you over if you're not at the very top of your game.