- 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
First of all, this class is very difficult. The assignments take time to figure out, and Dr. Eggert's tests are notoriously unpredictable and difficult. Plus, the assignment grading was super slow this quarter, with 3/6 assignments returned as of the start of finals week. I went into this class expecting the worst, but I actually learned a lot coming out of it. Though he doesn't give you much help on assignments, Dr. Eggert's lectures are incredibly engaging because of how much he knows about everything (he also casually throws insults at random stuff like mac users and c++ without intention, which is also pretty funny). Besides, the TAs are very helpful in terms of guiding you through assignments. By the end of the class, you will likely have learned many useful concepts and tools for industry (aside from emacs, sorry Eggert) as long as you try your hardest on all assignments. Plan around this class if you wish to take it - don't take this class with another difficult class. Plus, Dr. Eggert writes the assignments, but the TAs grade them with their own rubrics, so pay attention to Piazza posts about the assignments. Though grading is incredibly slow, the TAs (at least for this qtr) seem to be pretty lenient and won't give you too much of a hard time as long as you adhere to their rubric. Make sure you do your best on all the assignments cuz you are not getting 'em back until weeks 9-10. It was a very tough journey for me, but it was worth it.
As is well-known, this class was horrible. Labs almost every week with almost no direction and covering many disparate topics. I had Tameez Latib as my TA, and he was good, but there's only so much you can so when the content and structure of the class is so bad. It's a really great thing that this class was discontinued and replaced by CS 97.
I did not like this class very much. I thought the material was very very important, but I feel like the online format combined with Eggert's brand of more chaotic teaching methods were not a good fit. The TAs were really nice.
The most important thing I got out of this class was I made a bunch of friends doing the project together, and I feel like I got a good overview of SWE.
The worst part of this class by far was the tests and the very non-transparent grading. The test averages were abysmal. The curve was a lot harsher this quarter, too, probably because projects were worth more than usual (15% as opposed to ~5%).
Overall, 5/10 class. Get through it and you will be a better computer scientist. It's like a light hazing.
There's a project each week, so 10 assignments total over the quarter.
Each project covers that week's lecture of some new cs topic (i.e. shell scripting, ssh, linux, system calls). The projects really don't require much time, but each one requires that you understand that particular cs topic well and getting a good grasp of it in one week might be difficult at times.
The final is hard, but honestly pretty doable and partial credit is key to getting a solid score.
This class, even though they have made some assignments much shorter, is still a lot of work and the last assignment is worth 5% of your grade and you're only given a week to handle it ( with some research presentation and still trying to study for finals). Also, it doesn't help that his final will absolutely destroy you. Extremely difficult and just all round horrible. My best advice is to start looking on the material from now, give yourself a head start, you'll need it.
35L has a bad reputation for a reason. I just took CS 111, and the workloads are pretty much the same except for the readings--which is insane. The TAs try their best to teach whatever language you're covering in two days, but there isn't much you can cram of the basics of C/python/Bash in four hours while also covering the spec. The specs are often confusing and in the case of my specific quarter, wrong (we had to check a google doc instead for one lab). If you have a bad TA, just go to a good one--your grade depends on it! You don't get your grades back before the next project and a few rely on the previous project. There isn't a test script like with 111 so if your program is consistently slightly wrong, you're screwed. Also,The beaglebone is used once and it costs $100. Overall, this class is trial by fire.
Oh boy! Now that I've completed the infamous 35L, I legit feel like I am ready to tackle ANYTHING. This course is ABSOLUTELY broken, and no other will probably ever top this one. My man Eggert made ANOTHER new assignment this quarter (aside from the insanely impossible Assignment 9), and the workload became even harder than ever before.
I am glad that I took this during S20 -- probably the wisest decision I've ever made so far. The grading was much quicker than any of the previous quarters, and the final was MUCH simpler. The average is around 70%, which is honestly unprecedented in an Eggert course.
I somehow ended up with a raw score of 94% total, but that still wasn't enough to get an A+ in the class. Guess that was just never an option to begin with... :(
I will recommend my TA Ritam, since he was completely reasonable with the Assignment 10 grading, and his lectures are very informative. However, sometimes it will be useful to use slides from other labs as well -- since each TA makes their own, and the information often differs quite a bit.
Lastly, quote the TA Daniel:
"The almighty egg"
I thought this course would be way worse than it actually ended up being. They kinda fixed it a little bit by giving way more hints on assignments so you aren't just roaming the stackoverflow forest of information with no clue what to even search about. Now you have something to search before you mindlessly wander the internet trying to figure out the assignments. The assignments are still really time consuming ~10-20 hours per week and sometimes longer on the really hard assignments but the TA's did say assignment averages are higher this quarter because of the hints so they are clearly helpful. The final wasn't nearly as bad during my quarter (first corona online quarter) since the average was a 70 while eggert said he normally aims for a 50. It was less about c programming than past quarters and more about explanation of topics and how interactions would work. Ultimately I think the class is easier now but its still time consuming . That being said, I learned a ridiculous amount in this class and would recommend it because of how it just alters your workflow through technologies and software you can add to your repertoire.
35L is worth and important. People like to hate on the class, but ultimately the assignments hit important concepts and if you do them well, you'll learn a lot!
Comment on the final: if you don't get behind and learn the content of the assignments as they come, you'll still need to study for the final (for many hours). So, it will be tough and don't get behind.
Comment on the TAs: Joe Halabi, Daniel Meirovitch, Ritah Sarmah, Madhu K. were all competent imo. I think Daniel Meirovitch was the best and most experienced while Joe Halabi was the harshest grader (which only impacts Assignment 10). But any objectively graded assignments are curved across your section, so don't worry too much about that.
First of all, this class is very difficult. The assignments take time to figure out, and Dr. Eggert's tests are notoriously unpredictable and difficult. Plus, the assignment grading was super slow this quarter, with 3/6 assignments returned as of the start of finals week. I went into this class expecting the worst, but I actually learned a lot coming out of it. Though he doesn't give you much help on assignments, Dr. Eggert's lectures are incredibly engaging because of how much he knows about everything (he also casually throws insults at random stuff like mac users and c++ without intention, which is also pretty funny). Besides, the TAs are very helpful in terms of guiding you through assignments. By the end of the class, you will likely have learned many useful concepts and tools for industry (aside from emacs, sorry Eggert) as long as you try your hardest on all assignments. Plan around this class if you wish to take it - don't take this class with another difficult class. Plus, Dr. Eggert writes the assignments, but the TAs grade them with their own rubrics, so pay attention to Piazza posts about the assignments. Though grading is incredibly slow, the TAs (at least for this qtr) seem to be pretty lenient and won't give you too much of a hard time as long as you adhere to their rubric. Make sure you do your best on all the assignments cuz you are not getting 'em back until weeks 9-10. It was a very tough journey for me, but it was worth it.
As is well-known, this class was horrible. Labs almost every week with almost no direction and covering many disparate topics. I had Tameez Latib as my TA, and he was good, but there's only so much you can so when the content and structure of the class is so bad. It's a really great thing that this class was discontinued and replaced by CS 97.
I did not like this class very much. I thought the material was very very important, but I feel like the online format combined with Eggert's brand of more chaotic teaching methods were not a good fit. The TAs were really nice.
The most important thing I got out of this class was I made a bunch of friends doing the project together, and I feel like I got a good overview of SWE.
The worst part of this class by far was the tests and the very non-transparent grading. The test averages were abysmal. The curve was a lot harsher this quarter, too, probably because projects were worth more than usual (15% as opposed to ~5%).
Overall, 5/10 class. Get through it and you will be a better computer scientist. It's like a light hazing.
There's a project each week, so 10 assignments total over the quarter.
Each project covers that week's lecture of some new cs topic (i.e. shell scripting, ssh, linux, system calls). The projects really don't require much time, but each one requires that you understand that particular cs topic well and getting a good grasp of it in one week might be difficult at times.
The final is hard, but honestly pretty doable and partial credit is key to getting a solid score.
This class, even though they have made some assignments much shorter, is still a lot of work and the last assignment is worth 5% of your grade and you're only given a week to handle it ( with some research presentation and still trying to study for finals). Also, it doesn't help that his final will absolutely destroy you. Extremely difficult and just all round horrible. My best advice is to start looking on the material from now, give yourself a head start, you'll need it.
35L has a bad reputation for a reason. I just took CS 111, and the workloads are pretty much the same except for the readings--which is insane. The TAs try their best to teach whatever language you're covering in two days, but there isn't much you can cram of the basics of C/python/Bash in four hours while also covering the spec. The specs are often confusing and in the case of my specific quarter, wrong (we had to check a google doc instead for one lab). If you have a bad TA, just go to a good one--your grade depends on it! You don't get your grades back before the next project and a few rely on the previous project. There isn't a test script like with 111 so if your program is consistently slightly wrong, you're screwed. Also,The beaglebone is used once and it costs $100. Overall, this class is trial by fire.
Oh boy! Now that I've completed the infamous 35L, I legit feel like I am ready to tackle ANYTHING. This course is ABSOLUTELY broken, and no other will probably ever top this one. My man Eggert made ANOTHER new assignment this quarter (aside from the insanely impossible Assignment 9), and the workload became even harder than ever before.
I am glad that I took this during S20 -- probably the wisest decision I've ever made so far. The grading was much quicker than any of the previous quarters, and the final was MUCH simpler. The average is around 70%, which is honestly unprecedented in an Eggert course.
I somehow ended up with a raw score of 94% total, but that still wasn't enough to get an A+ in the class. Guess that was just never an option to begin with... :(
I will recommend my TA Ritam, since he was completely reasonable with the Assignment 10 grading, and his lectures are very informative. However, sometimes it will be useful to use slides from other labs as well -- since each TA makes their own, and the information often differs quite a bit.
Lastly, quote the TA Daniel:
"The almighty egg"
I thought this course would be way worse than it actually ended up being. They kinda fixed it a little bit by giving way more hints on assignments so you aren't just roaming the stackoverflow forest of information with no clue what to even search about. Now you have something to search before you mindlessly wander the internet trying to figure out the assignments. The assignments are still really time consuming ~10-20 hours per week and sometimes longer on the really hard assignments but the TA's did say assignment averages are higher this quarter because of the hints so they are clearly helpful. The final wasn't nearly as bad during my quarter (first corona online quarter) since the average was a 70 while eggert said he normally aims for a 50. It was less about c programming than past quarters and more about explanation of topics and how interactions would work. Ultimately I think the class is easier now but its still time consuming . That being said, I learned a ridiculous amount in this class and would recommend it because of how it just alters your workflow through technologies and software you can add to your repertoire.
35L is worth and important. People like to hate on the class, but ultimately the assignments hit important concepts and if you do them well, you'll learn a lot!
Comment on the final: if you don't get behind and learn the content of the assignments as they come, you'll still need to study for the final (for many hours). So, it will be tough and don't get behind.
Comment on the TAs: Joe Halabi, Daniel Meirovitch, Ritah Sarmah, Madhu K. were all competent imo. I think Daniel Meirovitch was the best and most experienced while Joe Halabi was the harshest grader (which only impacts Assignment 10). But any objectively graded assignments are curved across your section, so don't worry too much about that.
Based on 100 Users
TOP TAGS
- Tough Tests (42)
- Tolerates Tardiness (30)
- Has Group Projects (35)