Collegiality vs Teamwork and Digital Technologies

We re-aligned our computer courses last year.  Our school formerly was one of the few with a Computer Studies Department, with computer science and computer technology courses all existing under a single banner.  Last year the department was dissolved and computer science was put under the Mathematics Department while computer technology was re-integrated with the Technology Department.

I transitioned from Computer Studies Head to a co-head of Technology, but I'm finding working in such a diverse (we cover everything from metal work to food school to digital design) department challenging.  With so many horses pulling in so many directions, I can't help but feel that digital technologies tends to be a second thought.  Rather than feel excluded I've been finding ways to develop a stronger digital technologies continuum.

The computer lab has always been next to the design lab, though run by different departments.  Now that we're on the same team so to speak, I've been re-thinking how digital technologies, always minimally represented in terms of classes, should work within the school.  We've been developing an integrated digital technologies curriculum in order to facilitate that.

With the dissolution of Computer Studies the realigning of our school's digital technologies was inevitable.  No longer is Technology Design the lone digitally focused technology course in the department.  Combined with Computer Technology, our digital technology courses can now offer a continuum of learning across a wide variety of digital platforms.

I initially felt that dissolving the computer department was going to be bad for the discipline, but now I'm feeling a new synergy.

By drawing together our digitally focused technology courses under the many common threads they share we're able to offer 9-12 curriculum in a wider variety of areas.  For students in a rural area where digital-tech doesn't have the social impact it has in more urban settings this is a big deal.

The first step was to diversify our high-tech offerings.  I argued successfully at Heads for Tech-Design to offer Robotics (our tech design teacher has a background in it).  I also argued successfully for a Software Engineering option that would allow students interested in the field to experience industry standard practices around software development rather than the mathematics focus offered by computer science.

From the junior grades students get a wide variety of choice in 11 & 12 around what aspects of digital technology they want to pursue.  And even if the student isn't going into a tech-focused profession, they are at least able to develop the kind of digital fluency that will be handy in any 21st Century workplace.  Of course, digital-tech doesn't end at the workplace.  If we're going to graduate citizens capable of communicating in the 21st Century, they need to have digital fluency.

I always felt isolated as the head of computers with only a part time comp-sci teacher who wasn't interested in collaborating.  Now that I'm the co-head of tech, or perhaps Head of Digital Technologies fits better, I'm able to empower our tech-design as well as my own computer-tech fields and build a more complete set of options for our students to benefit from.

Change isn't always easy, but in this case I feel like it's led to a good place where teamwork and a common goal has replaced cold, distant collegiality.

A 9-12 Digital Technologies Continuum with a healthy variety of choice that will develop graduates ready to take on the challenges of the 21st Century:

The layout is so helpful I've expanded it out to the Technology Department as a whole:

The Lab That Isn't A Lab

I'm teaching Computer Engineering in a school computer lab.   It's the nicest lab in the school, and I don't want it any more.

I recently described it to my principal as, "trying to teach auto mechanics in a new car show room where you can't touch anything."

Computer engineering in school underlines everything I don't like about school computer labs (and that list is long).  I don't think school computer labs teach students anything helpful about computers.  In fact, I think they are specifically designed to be out of date, glitchy, inaccessible and frustrating - hardly the mindset you want to put students in when you're teaching them how to learn effective operation of an extremely powerful learning tool.

Essentially, what we try to do in school computer labs is teach students how to ride a bicycle by having a professional bike rider come in when they aren't there, maintain and ride an old bike, then leave it there for them.  We then tell the students to get on it and ride with no hands on experience, practice, training or intent.  We then get angry with them when they fall off and damage the bike, or ride it pointlessly in circles.

Whether it's media arts labs, or school computer labs in general, I'm not a fan.  The fact that they haven't changed significantly in form or function since I graduated from high school in 1989 should bother people, but the real bee in my bonnet is the lack of ownership in our understanding of technology.

If you want to use technology in your classroom (and in 2012 you'd have to bury your head pretty deep in the sand to not want to), then you the teacher need to understand how it works, and you need to teach this to your students.  The willful ignorance I meet in staff is sometimes good for my ego, but never productive in developing technical literacy in our students.

With our old tech, people are familiar enough to know what they are doing:

... but not so much with our new technology.  We need to address that.  Until we're all familiar enough with the digital tools we're expected to be literate in that their use is second nature, we need to spend time, especially in the classroom, learning what they are, and you can't do that in a school board IT straight jacket.

I'm not advocating for a ground up build your own computer when you want to type out an English paper (that's what computer engineering is for), but I am advocating for an open, author-able, stable, up to date system that allows teachers and students to become familiar with the options and customization available on this equipment (something impossible in our board, locked down, forget-everything-when-you-log-off terminals).

Back to the lab that isn't a lab.

When I was doing my AQ for computer engineering in the summer, our instructor showed us his new classroom in his new school.  It was fantastic.  Work benches filled it, fabrication tools and a few tables for the odd sit down talk.  It looked like a room where making happened.  There wasn't a single board computer in there.

Later in the summer, when I was picking up computers from a school in Guelph (a teacher, working in the summer?  Evidently), I saw their lab and it was the same idea: workbenches and stacks and stacks of parts; a room where hands-on learning happens.

I'm not entirely sure why we feel that computer engineering should be happening in a computer lab at my school.  My seniors don't use the school computers at all, and my juniors are only on them because they are there.  I'd much rather they be hands on with machines, except there isn't enough room in a lab full of school computers to make another network.

What do I want?  One of the de-labbed classrooms where there are plenty of electrical drops.  I'd be willing to evacuate the much in demand lab if I could get a room that let me store my equipment and set it up as I need; a room that was truly a lab where experimentation and hands-on discovery happens.