Second Observation
Today I met with the assistant principal to discuss my second Formal Observation, which was on Tuesday afternoon. In general, things were the same as on my last observation, except that he knocked points off in the "teaching critical thinking" and "applying Maine Learning Results" sections, and suggested that I give more handouts to the students so they wouldn't have to ask me so many questions.
The Maine Learning Results are a bunch of criteria such as "Collaborative and Quality Worker", and one of the graduation requirements is that students be familiar with the Maine Learning Results. According to my observer, I'm suppoed to be making sure the kids know which learning results they're developing during their assignments.
My first thought about this was, "this is bogus; I'm (a) already too busy making up 4 different curricula on the fly, and (b) if I say to the kids, 'this assignment will make you a Clear and Effective Communicator' they'll look at me as if I have 2 heads". Howevah, in the mind of the assistant principal, this is just to cover my ass if the State of Maine does a review of my program and asks to see how it relates to the Maine Learning Results. OK.
The second area was "critical thinking". It must be difficult to walk into a computer class as a non-computer person and understand anything that's going on, much less figure out whether or not I'm teaching critical thinking. My best guess is that he equated "students have to ask a lot of questions" with "they can't think for themselves" since when I asked him about it, all he could tell me was that he didn't see evidence of it.
I encourage students to ask lots of questions, which I usually "answer" with other questions. Some of them are now at the point where they can do some debugging. I do think they're improving at thinking critically. With some students, though, it's like pulling teeth. Follow these easy steps to take a walk in my shoes:
1. make a very detailed assignment handout, listing what the program should do, what variables and functions you'll need.
2. give out handouts.
3. go to answer a question and realize that the student has not read the handout (and usually needs to be prompted multiple times to read the handout). "I don't like to read" is a common response here. "Too bad" is usually MY response.
I struggled with how much information to give on handouts earlier in the year, thinking that I didn't want to do too much spoon-feeding, but I realized that I do need to do a good amount of very directed programming assignments (with details down to the methods and variables) for a while until the students get used to what a well-structured program looks like. Only once they've got that down will they be able to start thinking about good design.
His final comment, "are there notebooks the students can refer to instead of asking you?" made me envision a beautiful world where I have a textbook and a curriculum. I mentioned to him in our meeting that in the Glorious Future the students will have better reference materials than just the Java Documentation (or the JavaScript or MySQL or ColdFusion or HTML or whatever), but until there's a book on Java programming written for students who read at the 6th-grade level, I will be responsible for creating those reference materials (and/or creating materials to get these kids' reading levels up to the point where they could understand a Java textbook). Until then, things will be rocky.
Thank god it's almost Christmas. I need a week of sleep.







