Ratings for Computer Science 162
Based on 92 ratings for the instructor(s) that have taught this course.
Comment: The class must have changed a lot since Fall 2011, when it got a ridiculous number of 0 ratings. The class is quite organized, and Joseph is a clear and knowledgeable lecturer. Projects and homeworks were hard but good learning experiences (though sometimes poorly spec'd like in the last homework). Exams were straightforward but require some attention to detail. Even if you don't do the entire project, make sure to understand your group's parts because they might show up on the exam. And as always, get a good group.
Submitted May 21st, 2016
Comment: Kubi is a pretty good guy. You can tell the guy's either getting old or tired. There's no point to go to lectures because he stays stationary most of lecture (it's clear why if you meet him) and lectures were webcasted. The TAs were pretty bad though... Except for two of them, a lot of them didn't really seem to have great people or explanation skills. They occasionally gave blatantly wrong information at review sessions and I mean basic information... Furthermore, projects are such a pain. The whole idea of this course is to break up projects, but then the exams test your understanding of a specific component of the project that your partner may have worked on while you were busy working on another component so you end up not being able to solve it. Make sure you have a good group. My group screwed me over so bad and two of my partners still doesn't understand C, which made this class a nightmare for me...
Submitted Jan. 5th, 2016
Comment: My full-time fall internship with the company CS162 was the toughest technical experience I've had without any equal. The company's CEO John "Kubi" Kubiatowicz is excellent at getting concepts across in a clear manner with his biweekly tech talks. The 3 performance evaluations I had, which Kubi and the mentors disguise under the term "midterms" and "final", were quite grilling with high attention-to-detail questions, but I found that studying his tech talks and slides closely were sufficient towards perform above average and not get fired. The project I worked on had three stages with difficulty that increased on an exponential scale, but thanks to me and my team of 3 other non-procrastinating interns we hosted ourselves a 4-month long internal hackathon and finished with 0 out of 5 slip days left. Other factors towards the difficulty included 1) mentors (who preferred to be called "TAs"?) who couldn't help anyone since OS designs were pretty group-specific, 2) the C language has the dumbest conventions and is impossible to program in, and 3) Debugging with any kind of tools was unproductive and print statements only work as much as coin flips land on heads. All in all it was a very educational experience, as I've been able to move up to bigger companies, lose 20 pounds in the 4 months, and trashtalk Windows more.
Submitted Jan. 3rd, 2016
Comment: Pros of the class: -Kubi is a phenomenal lecturer, and is able to clearly and concisely explain dense material. -The homework and projects give you good opportunities to get your hands dirty at the operating system level. -The material is actual quite interesting on top of being very useful. -Exams are pretty straightforward (he likes reusing conceptual questions from older midterms). Cons of the class: -The TAs were all good guys, but terribly unorganized and not as helpful as one might hope in a cs class. It took them 2 weeks to grade both midterms, and a week and a half to finish grading after finals. It sometimes felt like they weren't really familiar with the projects either. -The last project, the file system project, took ages to complete. It was a new project, and the TAs didn't offer very much help on it. In fact, it took so long that my group didn't finish until finals week even though we worked on it every day during dead week.
Submitted Dec. 29th, 2015
Comment: Cool professor, however the class was extremely disorganized and had some of the most antagonistic/awful TAs. Homeworks and projects were often totally wrong with misleading instructions. TAs were also totally useless during office hours. Exams were also off from what he told us to expect in big ways. He was really enthusiastic and cared about teaching the class well though.
Submitted July 27th, 2015
Comment: This is definitely a useful class to take. All of the material is useful and relevant to software engineering. Kubiatowicz's exams are really straightforward. The projects are pretty interesting and not that bad - about 20 hours each (and there are only 3 projects). The homeworks are also pretty interesting and roughly take 8 hours each (~4 homeworks). That being said, you definitely need to get a good, disciplined, hard-working group. I know lots of people that got screwed and did the projects with fewer people (or by themselves). The TAs weren't that helpful, either. One of the assignments was riddled with so many grammar errors that it was pretty clear a non-native English speaker wrote it. This wouldn't be an issue, except that it was clear neither the professor or any of the other TAs had even skimmed it over. In lecture, Kubiatowicz knows what he's talking about, but the logical organization of the lectures (the topics covered, in what order, etc.) was absolutely atrocious. Slides were far too verbose. The material jumps around in a very disconnected manner. It was hard to make sense of it all and tie everything together.
Submitted May 16th, 2015
Comment: Culler is a super enthusiastic professor. He cared a lot about the class, and was very helpful. He is not a great lecturer, but he is definitely a good one. The class itself was undergoing restructuring, so there were definitely hiccups along the way. The projects and homeworks were cool, but tough and at times poorly specced out. But CS162 is a very worthwhile class!
Submitted May 15th, 2015