<p>This is my last semester and I'm going to take two CS upper divs to complete my minor. So far the only upper div I've taken is 188. Currently, my schedule consists of only one stats class I need for my Mcb major. Taking into consideration this years weird rules for upper div enrollment and looking at the schedule today, I actually have more class choices than I thought. What seems available to me that I'm considering taking are:</p>
<p>160
161
169
170</p>
<p>A little background on me is I haven't had an internship yet but I've been working on an app this summer. I plan to commute next semester which might make things hard for group project for 160 and 169. I pretty much know I want to take 170 because its a good foundation to have. But I want to hear people's recommendations on what two they would pick in my situation? Which two are the most useful in getting a job? Are all just as good so I should pick the one that interest me most? Any idea what 160 will be teaching this year? Is picking 3 of these classes too much in addition to my one stats class? Since I only need two to get my minor, maybe I can take three and take one of them as pass no pass.</p>
<p>I had 160 and 161 last semester…</p>
<p>160 teaches interfaces and design principles in general. The focus last spring was Android, in the past I think they’ve used Kinnect (and done a couple more android semesters). I’m not sure what the projects’ll be done on in the fall, but either way the concepts from the class’ll be the same, and it’ll focus on design iterations and user testing and such.</p>
<p>161 I thought was a lot of fun. I had Paxson, definitely recommend him as a professor though I doubt he’s teaching in the fall… I would suggest being pretty solid on the 61C concepts (assembly, stack organization, etc) if you plan to take 161. Overall a fun class, and generally applicable to different areas of CS, since attacks can come from so many directions.</p>
<p>169 should be pretty similar to 160, it’s a project class. You’ll be in a group, working on some HUGE project for hours and hours and hours throughout the semester. You should definitely NOT take 169 and 160 together.</p>
<p>I know a couple of people who did 160, 161, 170, and a humanities last Spring… they were pretty busy but it seemed mostly do-able. Project classes could be a pain if you’re not staying on campus though. In terms of useful skills, 160 and 169 will give you experience starting/working on huge projects and you’ll write lots and lots of code. 161 will teach you more material but won’t give you much general coding experience.</p>
<p>Honestly, I’d say just pick whichever classes sound like the most fun. But don’t try to do 160 and 169 together.</p>