Semester's over, stop stressing about your grades and enjoy summer. Above all, don't let Berkeley or CS61C get you down, because surprisingly enough, there are far more important things in life. Sorry to anyone whose regrade requests I didn't change, but I have standards I have to follow and while I try to be as generous as I can be within those standards and at least give some reward for effort, I can't overstep my bounds as a reader. Thanks to all for being patient with me and my slowness, and special thanks to anyone who appreciated my comments on homework. Not like anyone's ever going to read this again, but just felt like putting some closure to this page. Also, a silly face picture :P (I always wanted one like the TAs and Dan had, and now I have time to put it up myself just before my account disappears). I <3 my DSi.
I will try and make a compilation of common errors and general feedback for each assignment. This should hopefully be helpful for students and save me some time from having to repeat myself. If you received an error code in the comments section, look here. You will probably want to bookmark this page ^_^
My name is Ibrahim, and I'm a second year EECS major (woo!) Option V (General woo!) because who needs to specialize when EECS is so awesome? (*grumble* *mumble* grad school.) I love computers, and I love EECS, and I especially love CS61C. If I had a time machine or another body I would probably double major in Mechanical Engineering, but I don't have time for that unfortunately. Too many cool classes in EECS to take.
The best way to contact me is just to send an email to cs61c-rc@allthatinststuff. It'll automatically get forwarded to my main Berkeley account and be filtered into a folder nicely.
I'm an officer in HKN (yay!) so I hold tutoring/office hours every Wednesday from 2-3PM and every Friday from 11-12PM (and am generally in the office from 12-1PM) in 290 Cory. If you can't make it to one of the TA's office hours' or Dan's office hours or just want to talk about homework, feel free to drop by - I'm often lonely on Wednesdays :'(, although on Fridays the office can be busier because other classes have homeworks due. Since your homework is due on Wednesdays, it might be a good time to drop by! I can't guarantee I'll be able to answer your questions since I'm not actively following the lectures and whatnot, but I should be able to do a pretty good job.
In general: do work on time (!) and don't fall behind. This goes for any class, obviously, but you'd be surprised how often people don't do this (myself included :( ).
Know your C forwards and backwards, especially pointers and memory allocation/access. Your ability to understand assembly hinges on your understanding of the low level parts of C. Test your stuff in MARS when possible, and try to think of edge cases that would throw off your code, or just make sure that your code actually does what the problem specifies rather than simply solves the sample that is given to you.
When in doubt, draw truth tables, because they'll never steer you wrong (assuming you treat them well). More generally, if you're not sure of your answer or not sure what to do, try some examples.
When working in Logisim, use subcircuits as much as possible. It's just like writing functions in C, but people don't seem to like to do that much either. Abstraction is at the heart of CS, so use it wisely. Also, try to be neat about your circuits and when possible do things in a patterned way.
You can probably tell that I really like parentheticals, huh. It has nothing to do with Lisp, either, although Lisp is cool. I also apparently like silly emoticons.