- Home
- Search
- Paul R Eggert
- COM SCI 35L
AD
Based on 100 Users
TOP TAGS
- Tough Tests
- Tolerates Tardiness
- Has Group Projects
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Sorry, no enrollment data is available.
AD
Beware of this class! 35L drained so much of my time, so make sure to schedule your quarter appropriately. As others have stated, there needs to be some restructuring.
This class had 2 lab sections per week, with a lab assignment due at the beginning of each week. Attendance for these sections is not mandatory, and usefulness depends on ur TA. Labs 2, 4, 5, and 9 were especially time consuming for me, and all the other labs were still either difficult or annoying af. I turned in most of the labs late, so my lab average was about an 82. I did feel like I learned a lot from trying to do the labs, but this did not help at all for the final lmao. I pulled up with textbooks and hundreds of pages of notes and scored around the median (52), which got me a B. The final was 17 PAGES of the hardest shit ever. Each of the 10 questions were weighted equally and had to do with one of the labs. I straight up left a question blank after reading the directions lool and totally guessed on the multiple choice. There were basically no free points at all, so good luck on that lmao. 3 units does not correspond at all to the necessary workload of this course, and after hours and hours of work I escaped with a B. This class also takes hella time away from all your other courses, so be ready for that
Worst class that I've ever taken. The workload is insane especially for the first 6 weeks. It eases up a tad but then they had the worst assignment ever during week 10 (when the final is on the Sunday before finals week) that was so time consuming and hard that half the class didn't even do it. You're expected to learn pretty much a whole language/aspect of cs (bash, python, c, linking, git) and then complete super time consuming hw assignments showing "mastery" of a concept that you just learned. Also, Eggert doesn't teach the class. The TAs do, so if you get a bad TA then you're screwed. The only good thing about this class is the generous late policy. The final exam was terrible and scarring. I never want to take this class again and I never want to take an Eggert exam either. This class needs to be reworked. The workload can be cut in half easily especially for a 3 unit class. I made the mistake of taking this at the same time as CS 33 and the workload was insane. Worst quarter at ucla so far. I have no clue how I scraped out with a B but I don't want to think about this class anymore.
This class is a pain in the ass, but as long as you don't cheat (i.e., don't look at GitHubs), you'll learn some really important skills for industry. I'm currently doing an internship, and being comfortable with Linux, bash, ssh, and git is really helpful.
The class is TA-led, so how much you struggle depends on who you get. Regardless, prepare to do a lot of Googling and to read a lot of man pages to get through some of your assignments. The assignments take up a lot of time, but Eggert's late policy is very generous, so you're almost never strapped for time.
The final is fairly difficult, but you can bring as many notes as you want. I recommend finding notes from previous students and printing those out. They also give you practice exams and solutions to them, so you will know what to expect on the final.
For reference, I averaged about a 94% on labs and got 67/100 on the final. The average for the final was about 54, and the standard deviation was 14.
The other reviews are right. This class is a LOT of work. Labs are difficult. Lectures do not go over how to do them. You have to figure out a lot of it yourself (lots of googling). Discussions are also helpful, depending on your TA, with some good hints. Exams are also very hard, that's how Eggert exams are. Open book/notes, but somewhat more difficult conceptually (combine 2 ideas, pros and cons of a hypothetical program to create, etc), as well as some coding problems. Open notes helps, but not much. You need a good understanding of the material to succeed. Grading was very slow this quarter, we didn't have grades on any of the 6 assignments until after the final :/. Very untransparent, which was frustrating. All that being said, this class was VERY helpful. Eggert is a great lecturer, and incredibly smart. He definitely knows what he's talking about (ex: he coded part of emacs, which you use in this class). It's certainly difficult, and labs can be quite tedious, especially because his lectures just discuss the concepts/background of what you're doing, and you have to figure out the syntax/process. But I definitely am thankful I had this class, I learned a LOT. Might be an unpopular opinion, but I intend to take more classes with him (at least 131). You learn a lot in this class, and its a very valuable experience, potentially at the cost of a slightly lower GPA.
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.
Unclarity. Unclear lectures explaining anything vaguely. Unclear assignment specs that makes you wanna smash the computer. Absolutely ridiculous project that the professor teaches you nothing about, and you have to learn every single bit from online resources.
Beware of this class! 35L drained so much of my time, so make sure to schedule your quarter appropriately. As others have stated, there needs to be some restructuring.
This class had 2 lab sections per week, with a lab assignment due at the beginning of each week. Attendance for these sections is not mandatory, and usefulness depends on ur TA. Labs 2, 4, 5, and 9 were especially time consuming for me, and all the other labs were still either difficult or annoying af. I turned in most of the labs late, so my lab average was about an 82. I did feel like I learned a lot from trying to do the labs, but this did not help at all for the final lmao. I pulled up with textbooks and hundreds of pages of notes and scored around the median (52), which got me a B. The final was 17 PAGES of the hardest shit ever. Each of the 10 questions were weighted equally and had to do with one of the labs. I straight up left a question blank after reading the directions lool and totally guessed on the multiple choice. There were basically no free points at all, so good luck on that lmao. 3 units does not correspond at all to the necessary workload of this course, and after hours and hours of work I escaped with a B. This class also takes hella time away from all your other courses, so be ready for that
Worst class that I've ever taken. The workload is insane especially for the first 6 weeks. It eases up a tad but then they had the worst assignment ever during week 10 (when the final is on the Sunday before finals week) that was so time consuming and hard that half the class didn't even do it. You're expected to learn pretty much a whole language/aspect of cs (bash, python, c, linking, git) and then complete super time consuming hw assignments showing "mastery" of a concept that you just learned. Also, Eggert doesn't teach the class. The TAs do, so if you get a bad TA then you're screwed. The only good thing about this class is the generous late policy. The final exam was terrible and scarring. I never want to take this class again and I never want to take an Eggert exam either. This class needs to be reworked. The workload can be cut in half easily especially for a 3 unit class. I made the mistake of taking this at the same time as CS 33 and the workload was insane. Worst quarter at ucla so far. I have no clue how I scraped out with a B but I don't want to think about this class anymore.
This class is a pain in the ass, but as long as you don't cheat (i.e., don't look at GitHubs), you'll learn some really important skills for industry. I'm currently doing an internship, and being comfortable with Linux, bash, ssh, and git is really helpful.
The class is TA-led, so how much you struggle depends on who you get. Regardless, prepare to do a lot of Googling and to read a lot of man pages to get through some of your assignments. The assignments take up a lot of time, but Eggert's late policy is very generous, so you're almost never strapped for time.
The final is fairly difficult, but you can bring as many notes as you want. I recommend finding notes from previous students and printing those out. They also give you practice exams and solutions to them, so you will know what to expect on the final.
For reference, I averaged about a 94% on labs and got 67/100 on the final. The average for the final was about 54, and the standard deviation was 14.
The other reviews are right. This class is a LOT of work. Labs are difficult. Lectures do not go over how to do them. You have to figure out a lot of it yourself (lots of googling). Discussions are also helpful, depending on your TA, with some good hints. Exams are also very hard, that's how Eggert exams are. Open book/notes, but somewhat more difficult conceptually (combine 2 ideas, pros and cons of a hypothetical program to create, etc), as well as some coding problems. Open notes helps, but not much. You need a good understanding of the material to succeed. Grading was very slow this quarter, we didn't have grades on any of the 6 assignments until after the final :/. Very untransparent, which was frustrating. All that being said, this class was VERY helpful. Eggert is a great lecturer, and incredibly smart. He definitely knows what he's talking about (ex: he coded part of emacs, which you use in this class). It's certainly difficult, and labs can be quite tedious, especially because his lectures just discuss the concepts/background of what you're doing, and you have to figure out the syntax/process. But I definitely am thankful I had this class, I learned a LOT. Might be an unpopular opinion, but I intend to take more classes with him (at least 131). You learn a lot in this class, and its a very valuable experience, potentially at the cost of a slightly lower GPA.
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.
Unclarity. Unclear lectures explaining anything vaguely. Unclear assignment specs that makes you wanna smash the computer. Absolutely ridiculous project that the professor teaches you nothing about, and you have to learn every single bit from online resources.
Based on 100 Users
TOP TAGS
- Tough Tests (42)
- Tolerates Tardiness (30)
- Has Group Projects (35)