These are Frequently Asked Questions about the EECS 325 Exercise Submission Process.
Do at least 3 new submissions per week, plus fixing your old code. With 10 weeks in the quarter that typically leads to about 30 exercises plus their resubmissions. I grade based on effort and learning. I expect more from someone who starts with more advanced skills who can get good code done in 1 or 2 tries, than I do from someone who starts with less experience and needs practise.
You can have up to 3 new pieces of code in the queue. You can have more than 3 things in the queue that I haven't gotten to yet, but at most 3 of them can be things I've never seen before. There's no limit on resubmissions.
Never send more than one solution in a submission, unless it's a multi-problem exercise.
No. The goal is to show me the breadth and depth of your AI programming skills. That means showing you know when and how to write good recursive, iterative, and mapping code, numeric code, macros, and so on. In the first part of the course, you work on these generic skills. In the second, you work on applying them to AI-related problems. Don't get hung up on one thing. Stop occasionally and look over what you've sent to make sure you've covered the major topics.
Send me email or post to the CS 325 news server. Put "HELP: Ex. name of exercise" in the Subject field.
Absolutely. This is strongly encouraged, and supported by the Exercise Submission Queue. Just retract your old solution and submit a new one. Just don't fall behind with the new submissions.
At best, less than a day. At worst, 3 or 4 days. It depends on my workload and how fast submissions are coming in. The queue is longest at the start of the week.
No! Every submission you send me should be your own personal answer.
If you have an idea for an exercise, email it to me. Put "EECS 325 Exercise Proposal" in the Subject field.
If it seems appropriate, I'll create an entry for it on the Exercises page.
Comments? 
Send me email.