<p>Hey can anybody tell me what the EECS upper division requirements are? I cant seem to find it. Thanks!</p>
<p>20 units of graded upper-div technical (1xx)</p>
<p>One class must have a "design project" (basically every other class...105, 130, 140, 141, 150, 160, 162, 184, 186, and others)</p>
<p>Is that it? Dont I have to take a few courses out of my department or something? And if it is just 20 units of graded technical course, then cant i finish that in like 2 semesters??</p>
<p>Undergraduate</a> Notes | EECS at UC Berkeley</p>
<p>Everything about requirements can be found here.</p>
<p>orochi, about the site you gave me, is it me or is it that EECS upper division is easier than CS upper division?</p>
<p>I don't know about that notion. 20 units is about 5 classes. CS upper division requires 5 upper division classes. The only thing is, CS requires CS170, which is a pretty tough class, while EECS requires a "design project" class. I would rather take the former over the latter. It's debatable. Both majors are pretty flexible with their upper divs.</p>
<p>vicissitudes, doesnt CS require 27 upper division technical courses? Would you rather take EECS or CS? and why</p>
<p>bump for an answer</p>
<p>I checked the degree page, and you're right. You need 27 units for cs. Still very doable, about 6-7 classes in 4 semesters. Sure, it's technically only 20 for eecs, but no eecs major takes only 20 units of upper div tech anyway. The main difference is you don't have to take ee classes for cs (except 42), eecs is capped whereas cs is not, and different general requirements in Coe and l&s. If I had to pick one out of those two, I would probably pick cs because I hate ee. But that's just me.</p>
<p>Hey, well for EECS you have an option to go for the computer science path. So you can pretty much just take ALL cs classes to graduate with the eecs major right? Do you think EECS is getting less impacted each year?</p>
<p>I suppose...but then why not just do CS? And no, I don't think EECS is getting less impacted every year. Its demand peaked around 2000, when the dot com bubble burst. Since then, the number of CS graduates have been going down every year, and demand has been going up. However, in the past year or two, the number of CS graduates have started to recover. Plus, with the economy in bad shape, business might look less attractive to people who want to get rich quick, and Engineering/CS might start looking more appealing. So if I were to make a wild guess, I would say, don't count on EECS getting uncapped anytime soon.</p>
<p>I have a question, since its only 20 units of technical courses for upper div., cant you finish upper division in say, 2 semesters because most people take around 13-16 units per semester.</p>
<p>You certainly can. I completed my own EECS B.S. requirements within three years. As another poster said, many EECS students take extra classes to expand their skill sets and pad their resum</p>
<p>You still need 120 units to graduate. There are also other requirements, of which I'm fuzzy on. I know there's one CoE requirement where you have to take a lower-div and upper-div class in the same non-engineering department. In any case, most people don't take all EECS upper-divs for 2 semesters and that's it. That would be overkill. It's better to balance your schedule with some non-engineering courses. Also, like I mentioned, most EECS students take more than 20 units of tech upper-divs anyway. Doesn't exactly look good on your resume. I suppose you can just do the minimum, use lots of AP credits and graduate early...but why would you want to?</p>
<p>I believe its all about the degree. Also grad early, go to grad school early? Makes sense?</p>
<p>
[quote]
I believe its all about the degree. Also grad early, go to grad school early? Makes sense?
[/quote]
</p>
<p>If you're going into EECS just to blitz through the classes to get a degree as fast as possible, grad school (as least PhD programs) is probably not for you. People go into PhD programs because they genuinely enjoy learning for the sake of learning.</p>
<p>
[quote]
I've known several folks who've taken just about every core EECS class offered, on both ends of the department, and then went on to enroll in graduate-level courses as undergrads. Personally, I think there is a line between being enthusiastic and overly obsessive. If you're that passionate about EECS, you have plenty of time to specialise in graduate school. Most grad programs don't allow you to explore your interests and take classes from many different departments, so I feel that overspecialising as a undergrad is a wasted opportunity. Each to his own, though.
[/quote]
</p>
<p>Good point. However, the top PhD programs in the nation like applicants with a bit of specialization. My recommendation is that if you want to apply to some sub-area of EECS, try to (1) take at least 1 grad class in that field before or during 1st semester senior year, (2) do some research in that field, read at least 5 research papers. I've heard Artificial Intelligence, CS Theory are particularly competitive sub-fields of CS so you might have to specialize even more if you're applying to those.</p>
<p>Look, there's nothing wrong about graduating in three years. Some people just learn faster than others. By the way, a Ph.D in EECS is pretty much useless unless you want to be a college professor which wont pay that much. Im only interested in getting my Masters. I never said I'd finish it in 3 years, i was just wondering why everybody took 4 years.</p>
<p>I know a lot of EECS majors who came into Cal with AP and Community College credit up the wazoo and can easily graduate in 3 years. However, almost all of them decided to stay for 4 years because believe or not, to these people, learning is not just a way to boost your salary but also a fun and fulfilling experience.</p>
<p>To prove my point about how it is not difficult to graduate in 3 years, here's a potential schedule:</p>
<p>Assuming:
1) You have at least 2 AP sciences, AP Calc AB
2) You have taken at least 1 community college class</p>
<p>Fall Freshman
CS61A, Phys 7A, Math 1B, Humanity</p>
<p>Spring Freshman
CS61C, Phys 7B, Math 53, Humanity</p>
<p>Summer Freshman
CS61B, EE40</p>
<p>Fall Sophomore
EE20, Math 54, CS70, Humanity</p>
<p>Spring Sophomore
Phys 7C, EECS 150, CS170, Humanity</p>
<p>Summer Sophomore
Internship</p>
<p>Fall Junior
CS162, CS186, E190, Humanity</p>
<p>Spring Junior
CS169, CS164, CS160, Humanity</p>
<p>There ya go, you can do the math your self, but it should fulfill every EECS major requirement. Also, it hits all the classes that CS industries look for (162, 186, 150, 169) and gives you a free summer in your sophomore year to find internships.</p>
<p>"If you're going into EECS just to blitz through the classes to get a degree as fast as possible, grad school (as least PhD programs) is probably not for you. People go into PhD programs because they genuinely enjoy learning for the sake of learning."</p>
<p>Yeah...big time true. </p>
<p>"However, almost all of them decided to stay for 4 years because believe or not, to these people, learning is not just a way to boost your salary but also a fun and fulfilling experience."</p>
<p>In theory, I think I could've finished all my math degree requirements in my first year if I'd tried...definitely graduate by second year. WHY THOUGH! It's college, stick around, enjoy it, and try to learn something more. You're at an ocean of knowledge, and do you really want to work 1 extra year of your life before you die? You'll be working forever, I really think enjoying that extra year is good.</p>
<p>Now graduating early and going to grad school is a good option..but like Nine said, the remarks he quoted don't seem to indicate grad school is ideal for that person.</p>
<p>Summer Freshman
CS61B, EE40</p>
<p>Spring Junior
CS169, CS164, CS160, Humanity</p>
<p>these two semesters would be hell to most ppl.</p>