|
M 1/5/15
G
|
Period 2: No
class.
Period 5: Quiz, followed by Jeopardy Bingo.
|
|
|
T 1/6/15
A
|
Both periods:
Review for midterm exam. A review book (e.g., Barron's
AP Computer Science A, 7th Edition) is strongly recommended. There is no
additional written HW due today.
Both classes meet today. A quiz is likely each day this week.
|
|
|
W 1/7/15
B
|
Midterm review.
A quiz is likely each day this week.
Period 5: No class.
|
|
|
Th
1/8/15
C
|
Midterm review.
A quiz is likely each day this week.
Period 2: No class.
|
|
|
F 1/9/15
D
|
Midterm review.
Both classes meet today. A quiz is likely.
|
|
|
M 1/12/15
|
Your most
recent test (in hard copy) is available for pick-up if you wish in MH-102
from 1:00 p.m. to 3:25 p.m. Please note, you should have already received an
e-mail containing the PDF version of the graded test, as well as an analysis
of which questions you had the most trouble with.
|
|
|
T 1/13/15
|
No exams (power
failure on the Cathedral Close).
|
|
|
W 1/14/15
|
Midterm Exam, 2:00–4:00 p.m., MH-108. Exam will be pencil-and-paper only.
Some of the questions will be drawn from AP review materials similar to the
Barron’s AP review book.
Several students have asked whether a “cheat sheet” of notes will be
permitted. The decision, announced in the block 5 class last Friday, is that
you may use a double-sided sheet, maximum size 5.5 by 8.5 inches. This
information was confirmed in a general e-mail that was sent out on Monday,
1/12/2015.
|
|
|
M 1/19/15
|
No school
(holiday).
|
|
|
T 1/20/15
|
Makeup day for exams
originally scheduled for T 1/13/15.
|
|
|
W 1/21/15
C
|
Classes resume.
|
|
|
Th
1/22/15
D
|
HW due (both
blocks):
1. Please glance at the following recent articles from InfoWorld, a
publication for IT professionals:
5/21/2014: Employers
want Java skills more than anything else
1/8/2015: The
hottest tech skills for 2015: Security forensics and good old Java
1/14/2015: Good
news, Java developers: Everyone wants you
2. Read Lessons 34 and 35. This is only about 9 pages of reading. Reading
notes are required, as always.
|
|
|
F 1/23/15
E
|
HW due (both
blocks, even though Block 5 does not meet today): E-mail your part (b) code
from the midterm exam, including the public static int
line that starts the method, to Mr. Hansen. Only one submission per pair is
required, but you are on your honor
to write out the code using pencil and paper (TWICE, once for each member of
the pair) before you send the code.* Send the code in the body of an e-mail
message, not as an attachment. Use the following subject line, changing the
block number and the names Bar and Foo as
appropriate. Last names should be in alphabetical order. Don’t forget the
double underscore at the beginning of the subject line.
__Block 3 Pairs HW due 20150123 [Bar, Bill/Foo,
Frederica]
* It sounds silly to require handwritten code in the year 2015, but remember,
we have to practice for an exam in which all code has to be written, under
time pressure, using pencil and paper.
|
|
|
M 1/26/15
F
|
HW due (both
blocks):
0. If you have not already submitted last Friday’s assignment, please send
your code as soon as possible. Follow the instructions in the Friday calendar
entry, or ask your partner to send a joint submission that you both agree on.
(You need to have jointly worked through the code, line by line, in order to
send a joint submission.) Since you’re late at this point, please include an
explanation for lateness in your code comments. If your explanation is
reasonable, the point penalty, if any, will be minor. If your explanation is
unreasonable, the point penalty will probably still be minor.
1. Write Lesson 34 exercises #1-11 all (pp. 34-3 and 34-4).
2. Write Lesson 35 exercises #1-8 all (pp. 35-6 and 35-7).
|
|
|
T 1/27/15
G
|
Block 2: No
class.
HW due (Block
5): Write contest problems #1 through 5 on pp. 34-7 and 34-8, contest
problems #1 and 2 on p. 35-14, and the additional written assignments below. Note: If you can, please correct the
typographical error in #2 on p. 35-14, at least in your imagination.
Additional Written Assignment #1:
For each problem where it is feasible to enter test code into a compiler
(i.e., almost all of the assigned contest problems), enter the code and
execute it after you have already
made your best effort to find the correct multiple-choice answer. For each
problem where your original answer was incorrect, write a “lesson learned”
statement to yourself. Be polite. An example is shown below.
Sample “Lesson Learned” Statement:
Fred, you originally had choice E, because you thought that the row and col values were added together. The correct answer is
____ , because in that answer, only the col index
is affected. Lesson learned: Always double-check the “body” (a.k.a. payload)
of the nested loop to make sure you understand what it’s doing.
Additional Written Assignment #2:
State the typographical error in #2 on p. 35-14, and then explain, in a
sentence or two, why it is not always a good idea to correct typographical
errors in other people’s code.
|
|
|
W 1/28/15
A
|
HW due (Block 2
only): Do the 7 contest problems and 2 additional written assignments listed
in yesterday’s calendar entry. Also do the assignment below.
HW due (Block 5, plus Block 2 after completing the 1/27 written assignments):
Make a test suite for your midterm
part (b) code, and use it to verify correct operation. Make sure that your
test cases include all the different types of situations you can think of,
including maximal runs that occur at the beginning, middle, or end of the
input array. You may work alone or with your part (b) pairs partner, but
whichever approach you take, keep editing your code until it passes all test
cases and appears to be bug-free.
Optional mini-project 1: Instead
of printing out the results of your test cases and manually comparing them
one-by-one to verify correct operation, you can automate the process. In
other words, have your code run all the test cases (preferably in a loop
using a ragged array) and report “Success!” or “Failure!” automatically. You
will learn more if you do this.
Optional mini-project 2: If you really want to be creative and learn a
lot, a fuzzer calibrated with one of the canonical
solutions available online would be a wonderful enrichment project. This is a
fair amount of work. However, if you have aspirations to be an expert hacker*
or tester someday, writing your own fuzzer would be
highly educational and a boatload of fun as well.
* Ethical hacker, of course. See http://en.wikipedia.org/wiki/White_hat_(computer_security).
|
|
|
Th
1/29/15
B
|
HW due (Block
2): Read Lesson 36 (reading notes required), and attempt questions #1-9 on pp.
36-8 and 36-9. These questions will not be collected just yet.
Block 5: No class.
|
|
|
F 1/30/15
C
|
Block 2: No
class.
HW due (Block 5): Read Lesson 36 (reading notes required), and attempt
questions #1-9 on pp. 36-8 and 36-9. These questions will not be collected
just yet.
|
|