Recent Tutoring Session Reviews
"For this session, the student began by practicing some multiple-choice questions over the subject of classes. These included the appropriate use of overloaded methods, the use of Math class methods, use of String class methods, and error analysis as well as some more general questions that involved understanding what a piece of written code accomplishes. With the exception of the error analysis question, which was admittedly a very difficult one, he answered these with little trouble. With the remaining 30 minutes of our session, I asked him to complete a programming challenge I had selected for him. It was, by my estimation, the hardest or second-hardest programming challenge I had given him yet. Nevertheless, he approached the problem skillfully, and it was gratifying to see him reason through it, gradually making his solution strategy more intricate as he began to grasp other cases that his first attempts did not adequately cover. He was able to finish the challenge before the session's end, which I found impressive; other challenges of this level of difficulty had taken him an entire hour in the past."
"We covered the "Actor.java" file in-depth in a line-by-line fashion. Additionally, I explained the generic format of a method. We also briefly went over the sub-classes that extended the Actor class."
"We covered questions the student had after taking an AP practice test. These included the concepts of Arrays and indexes, for loops, recursion, and De Morgan's Laws."
"The student and I went over questions he had about his coursework before delving into an overview of data structures in Java. We focused on inherited methods, when/how to declare variables within a class, and the applications of arrays, stacks, and queues. Going forward he plans to practice writing programs that communicate between methods and work on following the flow of information as the code runs."
"The student was having trouble with an assignment that built on a previous assignment. When we started, it was apparent that he had made a mistake inside the Eclipse IDE. He was struggling to compile the correct version of his program. It seemed to stem from the way he cloned his previous assignment to generate the new one. All associations were still pointing to the old file. We had to rebuild the project and move things over from his previous zip file that he uploaded. Once we had this knot untangled, we focused the remainder of our time on expanding the two sub-classes required for the project. The mistake was unfortunate; however, this student learned something invaluable about the nature of programming. If you are not careful, moving forward could require everything be completely undone before you can move forward gain. It helps to stay flexible."
"The student worked on the final project. We combined the three short-term classes into one and combined the three long-term classes into one. We also created a user menu that accepts two arrays and displays a menu of options with valid entries based on the number of entries in the second array. The user option numbers are generated on the fly based on the number of entries in the second array, and acted as validation."