- Home
- Search
- Paul R Eggert
- COM SCI 35L
AD
Based on 151 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
The difficulty in 35L is lies in not in the projects, but in understanding the content. Like many have suggested before the quality of the TA fluctuates significantly for any given quarter. Also since there is a new assignment every week on a new subject area, it may be harder to grasp a concept in only 4 hours of class time. That being said, Google is your best friend for this class. There is definitely a lot of resourceful documentation available online for each topic because the scope of this class is introductory. However, I would recommend only limited to no use of Google for assignment 1. That way you gain a better understanding of navigating the Linux man pages.
The assignment that took me the longest time was assignment 9. I found this link useful: https://computing.llnl.gov/tutorials/pthreads/ . Try drawing parallels with parallel computing in CS33(OMP and CUDA).
Other recommendations:
• Take advantage of Piazza (an online forum) that we will be using for this class.
• Use some sort of virtual machine (ie VirtualBox, VMWare Player,etc). Dual booting is really annoying.
• Sounds lame, but bring some sort of Linux/Shell Scripting textbook to the final(it’s open book and notes). Unless you’re already some godly guru, having this reference is invaluable
• Learn HotKeys for Ubuntu/Vim/Emacs ie.
o In Ubuntu:
Alt-t to open terminal
Ctrl-Shift-t to create new tab
Alt-number to navigate between tabs
Reflections: I came into this class having little to no experience with Linux and CLI(Command Line Interface). At first Vim/Emacs may seem difficult at first, but you’ll be fine once you get in to the flow of things. Although this class is only 2 units, the stuff you learn is pretty practical. Good luck!
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.
The difficulty in 35L is lies in not in the projects, but in understanding the content. Like many have suggested before the quality of the TA fluctuates significantly for any given quarter. Also since there is a new assignment every week on a new subject area, it may be harder to grasp a concept in only 4 hours of class time. That being said, Google is your best friend for this class. There is definitely a lot of resourceful documentation available online for each topic because the scope of this class is introductory. However, I would recommend only limited to no use of Google for assignment 1. That way you gain a better understanding of navigating the Linux man pages.
The assignment that took me the longest time was assignment 9. I found this link useful: https://computing.llnl.gov/tutorials/pthreads/ . Try drawing parallels with parallel computing in CS33(OMP and CUDA).
Other recommendations:
• Take advantage of Piazza (an online forum) that we will be using for this class.
• Use some sort of virtual machine (ie VirtualBox, VMWare Player,etc). Dual booting is really annoying.
• Sounds lame, but bring some sort of Linux/Shell Scripting textbook to the final(it’s open book and notes). Unless you’re already some godly guru, having this reference is invaluable
• Learn HotKeys for Ubuntu/Vim/Emacs ie.
o In Ubuntu:
Alt-t to open terminal
Ctrl-Shift-t to create new tab
Alt-number to navigate between tabs
Reflections: I came into this class having little to no experience with Linux and CLI(Command Line Interface). At first Vim/Emacs may seem difficult at first, but you’ll be fine once you get in to the flow of things. Although this class is only 2 units, the stuff you learn is pretty practical. Good luck!
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 151 Users
TOP TAGS
- Tough Tests (68)