- Home
- Search
- Paul R Eggert
- COM SCI 35L
AD
Based on 150 Users
TOP TAGS
- Tough Tests
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.
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
This course is kind of hard and tedious. I was only able to finish all of the assignents by going to my TA's office hours. For me, the hardest assignments were weeks 2,3,5, and 9, so start early on those. Googling topics was helpful, especially for the 2nd and 3rd assignments. This link was helpful for the Python assignment: http://docs.python.org/library/optparse.html
The assignments are ok in terms of work and difficulty. The experience of this course depends almost entirely on the TA that you have. Avoid a bad TA at all costs. My TA for this quarter can't explain things as clearly. What's worse, the grading procedure is like, each TA has about three assignments to grade. My TA spends almost the entire quarter to grade his first assignment. But it turns out he just uses two test cases, which means if your code has a tiny flaw and happens to fail his one test, you get 50% of the grade. I understand only the perfect code deserves full credit, but I can't imagine what is more unfair than to have your grades depend in such a big proportion on luck, given that everyone has a chance to make small mistakes.
Ok, so I'm about to graduate and I'm writing in response to the people that say Eggerts 35L is too hard and will hurt your gpa. Firstly, if you're struggling with 35L you should probably just change your major, because frankly, 35L is probably one of the easiest classes you will take in your undergraduate cs career. Secondly, get used to shitty specs, they will only get worse, just wait until you take 131.
This course is kind of hard and tedious. I was only able to finish all of the assignents by going to my TA's office hours. For me, the hardest assignments were weeks 2,3,5, and 9, so start early on those. Googling topics was helpful, especially for the 2nd and 3rd assignments. This link was helpful for the Python assignment: http://docs.python.org/library/optparse.html
The assignments are ok in terms of work and difficulty. The experience of this course depends almost entirely on the TA that you have. Avoid a bad TA at all costs. My TA for this quarter can't explain things as clearly. What's worse, the grading procedure is like, each TA has about three assignments to grade. My TA spends almost the entire quarter to grade his first assignment. But it turns out he just uses two test cases, which means if your code has a tiny flaw and happens to fail his one test, you get 50% of the grade. I understand only the perfect code deserves full credit, but I can't imagine what is more unfair than to have your grades depend in such a big proportion on luck, given that everyone has a chance to make small mistakes.
Ok, so I'm about to graduate and I'm writing in response to the people that say Eggerts 35L is too hard and will hurt your gpa. Firstly, if you're struggling with 35L you should probably just change your major, because frankly, 35L is probably one of the easiest classes you will take in your undergraduate cs career. Secondly, get used to shitty specs, they will only get worse, just wait until you take 131.
Based on 150 Users
TOP TAGS
- Tough Tests (67)