<p>One of these:
Math 61
Arts & Architecture 10
(or CS M51A)</p>
<p>and depending on the combination of the above classes, I may considering adding in Korean 1 or Chinese 1 or a GE.</p>
<p>Question is, how bad would my quarter be if I took CS111 and 131 together? I took CS33/35L/Physics 4AL this quarter and didn't have too much fun... so for those of you who've taken these courses, how does the work load compare (to 33/35L/4AL)? And if I were to just take one CS course (131 or 111), do you have any recommendations for others [CS] courses I should take? I've only taken 31/32/33/35L and it seems that most upper division courses require that I take 111/131/M51A first (adding M51A would mean a time conflict with A&A 10 and/or Math 61) Thanks in advance! :D</p>
<p>CS 111 isn’t as hard as people make it out to be. If you got an A in CS 33 then you can easily get an A in CS 111. In my opinion, projects for 111 took less time than CS 33 just because you’re given skeleton code for pretty much every project and if you’re unsure of what to do you can usually google for the topic the project is on and find example code that is similar to what you have to do. I haven’t taken 131 so I can’t compare it.</p>
<p>Also, if you take 111 and 131, definitely do not take M51A as the fourth.</p>
<p>^Can we? I just looked at the HSSEAS CS FAQs and it says we can try petitioning out of it if we recently transferred into the school and/or major… I wonder how they evaluate the petitions though.</p>
<p>and bump, anyone else willing to share their opinions on CS111 and 131? thanks!</p>
<p>Do NOT take CS131 and CS111 in the same quarter (unless you’re a programming genius like imrightuarewrong). IMO, CS131 is the hardest class I’ve taken so far at UCLA (since you not only have to learn about 6 languages, but be able to write pretty difficult programs using each one). </p>
<p>CS111 was pretty tough to me, especially since I had a lot of other responsibilities going on and didn’t have a lot of time to code with my “partner,” so we decided to split up the projects between the two of us. </p>
<p>Anyways, CS111 and CS131 is supposed to be two of the most time consuming core classes, so I’d try to split them up if you can. I’ve never had to take more than one programming class in a quarter yet…and I’d like to keep it that way.</p>
<p>Most people find CS111 hard because the topics covered in the class are specific and low-level (compared to the topics taught in CS32 - OOP principles). I agree that CS33 is also extremely low-level, but the topics are extremely basic and the projects are still like typical classroom assignments (solve a specific problem, etc).</p>
<p>The projects in CS111 are more practical (p2p, deadlocking issues, etc) which require a deeper understanding in the concepts taught in the course. Although skeleton code is provided, it still takes a decent amount of time to understand what exactly the skeleton code does. There’s documentation in all the provided files…but each project has a few files (which may require a lot of jumping around to refer to certain functions and variables). And believe it or not, but not everyone understands the provided skeleton code.</p>
<p>The projects are also supposed to be longer, which is why they allow you to work with a partner. Aside from the projects, you may have difficulties learning how to actually work with a partner (different styles, schedules, objectives). </p>
<p>If you have Professor Eggert, the exams are in a different format than those given in the CS30 series. His exams are more conceptual and test your understanding of the topics, not just some easy algorithm problems that you can whip up in a few minutes.</p>
<p>
Except for the design project.</p>
<p>Side-note: I’m a CSE major so I’m not required to take compilers (CS132), so in my curriculum, CS111, CS131, and CS152B are the hardest (CS) core classes that I have to take for sure.</p>