TO ALL CST 112 students:Since we will not be meeting in-person in the classroom (after classes resume, Monday 3/30), lessons, presentations, assignments, etc. will be provided "in the cloud" via this website. You should continue to submit projects, exams, etc. in your folder, but our "Code Reviews", Labs, and other interactions normally done in the classroom will instead be carried out using one-on-one telephone conversations I have been trying to telephone each of you, individually (using phone numbers from the class roster), to explain how we will work together under the new "Remote Learning" procedures, so that you can complete this course, satisfactorily. If you have NOT yet had such a discussion with me via telephone, please send an email to me at bam@professorbam.com, including a telephone number and times when I can reach you. Whenever you need help and/or have some new code to review -- rather than waiting for scheduled class days or times -- just run it in the Processing PDE (to make sure it runs!), then upload it to your folder, and call my cell phone. If I'm available, we can do an impromptu Code Review session (while the code is still fresh in your mind!); if not, just leave me a voicemail including some timeS when you will be available for me to call you back for Code Review. To satisfy "participation" requirements for this course, I expect each student to participate in a code review session a couple of times per week. If conventient, these may be on the same days as classes were scheduled (Monday/Wednesday or Tuesday/Thursday), but they can also be done on any other day (including weekends) and other times (between 9am and 9pm).
Take care and be safe.
|
|
Be sure to check the "CST 112 NEWS" page, regularly,
for further instructions. |
|---|
At this point, you should be creating object class definitions and working on code for Project #2 (which was assigned before the break).
Don't bother fixing or making improvements to Project #1 (nor to your q1/r1/s1 code); instead, work on Project #2, to get acquainted with Object-Oriented software design. (If your p2 code fixes something that was broken in your p1 code, it will count for both!)
Don't try to do all of Project #2 at once! Instead, just build one or two object classes, get them to work, add some more, and fulfill the Project #2 requirements step-by-step, running and perfecting each small change as you go.
|
"WhiteBoard" |
When you have completed a new piece of code to show off -- or if you need help -- call me for a "Code Review" session!
Previous announcements:
Please have a preliminary version of your code for Project #2
available in your folder during the week of March 23rd,
and be prepared to present your p2 code during "Code Review".
Click here for college alerts regarding the Wuhan Virus. |