ECE 264 is a definite ramp-up compared to CS 159 so do not be overconfident when going in unless you have actual experience with C programming. In Spring 2019, the course was structured as 50% - programming assignments and 50% - exams, so it's imperative that you're knowledgeable in both coding and concepts. While Prof. Wang was my professor, our section still did Professor Quinn's programming assignments which were complex and often had errors/bugs (so much so that students were given extra credit to point out mistakes in his assignments). Professor Quinn's assignments were time-consuming and you won't pass the class if you wait till the last day to do them or if you do not watch lectures. Regarding Prof. Wang's exams, they were fill-in-the-blanks exams. (i.e. she'd ask what a printf sta...read more

Prof. Wang is incredibly nice and if you go to her office hours, she's very understanding and will help you out with your program. However, her lectures are often hard to comprehend because of her accent + monotonic voice. Still, I'd opt for Prof. Wang over Prof. Quinn because her exams are much easier. I'd watch Prof. Quinn's lectures though...

Watch the lectures and do NOT do the programming assignments a day before it's due. Also, don't cheat because the professors do a mass plagiarism check on everyone's program at the end of the semester and some students got caught for an early assignment when they worked hard throughout the semester.

Professor Wang > Professor Quinn.

It was a lot better than expected. Its definitely improved since the summers before. There were some course organizational things but the lecturer was very flexible and willing to change things for students. Our first exam was apparently a total failure (50 minutes to download, write a program from scratch + test cases, and submitting), but they adjusted and gave us a longer exam for 4 hours. Surprisingly, I learned a lot. Definitely a step up from CS 159. There was a programming assignment every 5-6 days and plenty of extra credit (4 assignments). Feedback on these assignments sometimes took a while, especially at the end (but honestly the feedback was just auto-grader so it wasn't that helpful).

He explains things pretty well, but some lectures weren't as organized (i.e. some lectures was spent just debugging code he wrote in class). He is also usually quick about email replies and regrade requests.

If you can't start a programming assignment early, at least read through it and think about it. Sometimes just more time thinking about a solution makes the whole process faster. I think most of the people that didn't do so well in the course had a lot of other commitments that made it hard to keep up. Do the practice exam question like you would do the exam (timed). It is good practice and it is possible you might be able to modify the test cases in the practice exam to fit the actual exam. Brush up on some vim and unix commands.