Showing posts with label Thinking. Show all posts
Showing posts with label Thinking. Show all posts

Thursday, July 25, 2013

My CSTA Convention Experience

This has been such a busy summer with lots of wonderful PD opportunities. One of them was the Computer Science Teacher's Convention (CSTA, #CSTA13) in Boston.

I work for a small high school, under 500 students. At the convention I discovered that for the size school that we have, we are unique in our Computer Science offerings. In fact, most schools our size do not have a teacher dedicated to Computer Sciences, and computer classes are often taught by business or math teachers. If I didn't already feel isolated enough as the only CS teacher in my school, that only made the isolation feel even larger. I often do not have others to bounce my ideas off of in my building related to my subject matter. That leaves me to read a lot of other people's blogs, articles, follow others on Twitter, etc.

So going to the convention allowed me to connect to others of my ilk and gather so many wonderful ideas to take back with me.

Back in March of 2012, I blogged about the new APCS course being offered. I only knew what I was reading about it, I didn't know anyone involved in it. At the convention I was able to get a great deal of information about it and I want to look into more PD so I can become certified to teach it. One of the things I like more about this course than the current APCS A offering is that it is not a multiple choice heavy exam. It is portfolio based.

I also like that the AP Principles course promotes critical and analytical thinking, much like the Exploring Computer Science (ECS) course, another area I'd like to get more PD in. I also think the ECS course is a wonderful feed in to the AP Principles course. The thinking skills in these course really serve the 21st century "just in time" skill set, versus the 20th century "just in case" skill set.

Another thing that I have always believed and was only confirmed at the convention is that there is a difference between COMPUTER LITERACY (CL) and COMPUTER SCIENCE (CS), but literacy is often what is taught under the name of science. CL is to CS as spelling & grammar skills are to writing a novel. Yes, one must be literate in the one to accomplish the other, but knowing how to spell and form grammatically correct sentences does not make me a novelist. Writing a novel is a craft that some are born to to naturally, and others have to train to do correctly. CS is like that too, and we see that in the classroom with the skill sets students come in with.

So what is CL? CL is the ability to use a computer, the tool, with confidence. Most of us are literate. Our phones function as small computers, anyone reading this can use a browser and find a blog, we check and answer emails, and can use most office software.

So what is CS? CS is the ability to make the computer do the things that a CL audience will use. The CL person may use Microsoft Word to create a brochure, whereas, the CS person will design the embedded spell check for Microsoft Word. So to be able to stand by your program of studies and say that you are teaching Computer Science, then you have to be careful that you are not really teaching Computer Literacy.

So where does the shift begin? Hadi Partovi was a keynote speaker at the convention. He has heard the call for action and started the code.org movement. This December during Computer Science Education Week (CSEd), Hadi has challenged us to introduce new people to programming for one hour that week. This can be done individually or as group instruction. The site says students, but he stressed that it can be anyone, not just the kids. This will help bring awareness to Computer Sciences as a platform for the creating of new products through critical and analytical thinking. If we reach 100,000 people, and 10% of those people get turned on to programming, that would be 10,000 people who would have never considered programming as a reality for them before the challenge. With 1.4 million jobs in Computer Science predicted for 2020, and only 400,000 students graduating with Computer Science degrees, those 10,000 newly prospective CS students just seems a whole lot smaller than we need to fill that gap. (code.org) Reaching 100,000 is the goal, but what if we could reach 500,000, or even 1 million! Our 10%+ pool of possible CS students grows expediently as well.

Attending this convention made me realize that it is important for me to do more outreach and advocate for CS as a consideration for our students. I want to promote it during CSEd week. I want to go spend a day with our middle school students and program with them so they'll be excited to take it here at the high school. I want to start a computer club so students can get hooked on programming through game design. I want to make CS seem like a no-brainer when they select what courses to take each year, because I want them to see an importance and a relevance in their lives and society. I want them to see CS as a possible career, not just a graduation requirement.

Most of all, I don't want them to be passive users of their devices, I want them to be passionate about all the possibilities their devices can provide. I want them to see the flaws or failings in these devices, and I want them to fix those. I want them to create the things that only exist currently in Science Fiction novels. I want them to take technology to the next step so our global society can thrive.


Thursday, March 8, 2012

New AP Courses

Ed Week blogged about two new AP courses that will be offered in some pilot schools. One of the AP courses will focus on critical thinking skills and the other will focus on research skills. One of the things I thought was interesting in the blog is that it stated "The research courses are not designed to replicate a college course, but rather prepare students for college-level work and be an indication of readiness for elite college admission."

I agree that these are skills we do not focus on exclusively in a course designed for them (although it is my belief that we should) because most schools assume that these skills are being interwoven into the current curriculum. I think the assumption is there because they tell us that it is important. They tell us to ask questions that promote critical thinking skills. And if a student can produce the desired outcome at the end, then it is assumed that they had to think critically to do that.

I believe that instructors are trying their best to bring critical thinking to the classroom, but may lack the training to do so. But what is the real evidence that critical thinking is being evaluated properly in our secondary schools? The blog quoted Packer as saying "[college admissions officers] said U.S. students are not coming to college having developed research skills and the ability to integrate knowledge across a variety of academic disciplines". I have not sat on a college admission board but I can say from my experience in a classroom that many students do have difficulty pulling from one subject and applying it into another subject without a great deal of prompting and guiding.

Sometimes it is true within the same discipline!

In my programing class, which is a high level thinking and critical problem solving class by nature, I set up the formative assessments by levels (1-4). At level 1 there are fill in the blank questions, sometimes matching, sometimes multiple choice. I consider these warm up questions. Level 2 will usually ask a student to find erroneous code and fix the problem. Students can usually plug the code into the compiler, have the compiler find the problem and fix it until the code runs. Still a bit assisting. At level 3 is when I get the most questions. Level 3 usually presents code that they are told is broken, then they are asked "Why?"

It's giving the explanation as to why the code doesn't work that throws them. They often ask if they can just put it in the compiler and run it, fix it and give me the results. It is the knowing of, and explanation of why the code doesn't work that I can tell they have a deeper understanding of how the code is functioning. I explain to them that the compiler can't find everything wrong in the code and if you run bad code, you get bad output. Unless you can understand, just by looking at it, why code might not work, then you can become a better troubleshooter. Level 4 is the backwards engineering of the program. All they get is an output screen and a few guidelines on how input is expected to be gathered and they are released to create the program from scratch. Do they like this? NO. Do they do it? YES. How do they feel about it when it is done? Amazing! Their is so much joy in their face when they accomplish that level 4 task because it was not only a test of their doing, but of their thinking as well. Once a student starts a level 4 task, I have never had one give up. They become fully invested.

I applaud the idea of these AP classes but at the same time I feel that it would be more beneficial to do this type of work with students from when we get them as 9th graders until they walk across that stage 4 or 5 years later. Critical thinking, problem solving and research skills are needed at all levels in our adult life. Offering it as an AP class will only draw those kids who are college bound. Since it is such an integrated part of life, it should be just as integrated in our teaching and we need more creative professional development in the field to show us how we can integrate it into our curriculum without losing the time we need to cover all the important items in our curriculum.