<p>Hi all,
I will be taking EECS 183 this coming fall and was wondering if anybody could shed some light on the workload of this class? </p>
<p>Just a quick background, I only have about 4 months of programming experience, mostly in Python through the Rice Coursera course and an ebook for about three months. I dabbled a few weeks in Java (mostly just going over syntax), a few days in JavaScript, a few days in PHP, a few days in HTML/CSS, and a few days in C++. </p>
<p>Would really appreciate suggestions from someone with no/very little background who took this class. </p>
<p>I had even less experience than you when taking EECS183 and I thought it was all very manageable. Just make sure to do most of the CodeLabs even if they’re not required (you only need ~350/510) because they’re good practice. Some of them are very tedious though, so I skipped those.</p>
<p>The instructors go very slowly in the beginning so everyone can better understand the material, especially those who have never coded before. The projects took me between 1.5 - 20 hours for each one, but you usually have at least 9 days to complete them. The longer ones have more time before they’re due. Just do a little bit each day and the projects should be manageable.</p>
<p>@parentOf2018, thanks a lot for the survey, it is immensely helpful. Wow! Object oriented programming, one class that I’m interested in, gets a whopping 3.9/4.0, albeit the sample size is quite small but that says a lot. </p>
<p>@decoy, glad to hear that it was very manageable and I will surely keep those tips in mind. Did you go on and take EECS 203 and 280, if so did you do them concurrently? I hear most students do those two concurrently in order to go for 281 the following term.</p>
<p>Don’t take the numbers absolutely. I’d say the workload of EECS 270 is roughly double the workload of EECS 203, though 270 is rated 2.36 and 203 rated 1.94. Not that big a difference. EECS 477 is roughly 2/3 the workload of EECS 280 in my experience, but actually has a higher number. But yes, 381 is a tough class. </p>
<p>It should be quite easy for you considering you have prior experience. I had about 3 weeks of Python experience from Codeacdemy and I knew the material for the first third of the class.</p>
<p>The projects were pretty light. They took around 3-12 hours for me. Debugging will be the most time intensive aspect. You should be fine.</p>
<p>@Jay520, thanks, yeah, hopefully I will manage because I plan on taking 203 in the fall 2014 as well, and I’ve heard some horror stories about that one. </p>
<p>@thelostring I have Gibson. I’m not sure how good he is going to be though. The students at USC really liked him, but it appears that this will be the first time he teaches this course. He usually teaches video game development classes.</p>
<p>As a parent who is dropping $50K per year for my kid to go to UMich, he/she better be attending every single lecture/discussion session there is for each class they are enrolled – whether it is a 8:30AM class or a 7-9PM Friday laboratory or not. Time to go up</p>
<p>@Miw140 they do track attendance by making you answer in-class iClicker questions. You need to attend at least half of lectures, but the lecture that you attend does not matter.</p>