One of the first things I learned when I stumbled into the world of education (after a stint in the world of corporations) was that when you have a 42 year old building and 21st century technology, things don't always work.
And that's being nice.
The District is building a lot of new buildings, due to our regional population explosion, and all these new buildings come with what they term Model Classrooms. They're awesome. They have document readers, sound systems, DVD players, big fancy screens, you name it. These work wonderfully in the new buildings because the buildings are designed to handle this equipment. Last year I was one of ten teachers in our building to get a Model Classroom (because I happen to be one of the ten teachers that was considered a "tech head" by the administration). This meant that they had to fit all this fancy technology in a room that not only wasn't really wired well, but wasn't even square.
When I came back to my room that August, I discovered that all the wires and hook-ups for the Model Classroom were on one wall, and all my network wires and hubs were on another wall. This is not an ideal situation. No one has ever been able to tell me why this was done this way and everyone that walks into the room, and sees this comments on how "this doesn't make any sense." This meant that my phone and printer were on one side of the room, but my computer and document reader were on another side of the room. In addition, the only way I could get my computer hooked up to the network, was via an airport.
I put in a work order to have a network cord run through the ceiling and dropped down next to the Model Classroom wiring so I could hard wire my computer. I was told by our tech person (who shared us with 3 other buildings so you saw her maybe once a week) that "there' s no way I'm messing with that Model Classroom stuff because I don't know anything about it." Not the answer I needed. I would put in a work order every month or so and was always told that "we don't mess with that Model Classroom stuff, we'll have to contact the vendor." And it never happened.
I ran all of last year on an airport which worked okay (not great, but okay) because I had a Mac computer. It was an Apple airport. They seemed to communicate fairly well. The lab I tended to use was all Macs, so there wasn't any huge problem. Mild problems, yes, but major, no.
And then we got a new Big Wig in Technology and it was decided that we needed to be weened off of Macs and go to Windows systems and all of a sudden there were Dell computers everywhere. Our team got a lab assigned to us (which means one lab for 6 people as we share it with a special ed teacher) and it was a Dell, so when some of us with old computers were issued new ones, we could go with Dells or Macs, our choice. Mr. Social Studies and I, who were both used to Windows systems, went with the Dells. We quickly learned that most of our technology staff knew nothing about Windows operating systems or Dell computers, so we were left hanging quite a bit of the time. Not a good situation. About the only good thing I noticed was that our former tech rep apparently refused to work on Dells as well and was no longer with the District.
Keep in mind this is the same technology department who told us not to plug anything in at the beginning of the year because they'd send around "experts" to help us...and they screwed up the network.
It rapidly became apparent that running these Dell computers off of an Apple airport didn't work very well at all. Getting an internet connection was tricky in the first place, and then it tended to drop off several times during a basic 45-minute class period. This drives the kids absolutely nuts. They'd be working on something like Study Island (which is an awesome program) and they'd be in the middle of a game and they'd lose their connections. When you only have 45 minutes to do something, and you spend well over half of that trouble-shooting technology, even the kids tend to not want to use the computers. We were told by the Tech Department that we needed Cisco routers and they were on order and they were coming.
In the meantime, I was having major computer issues with my Dell. Because I was still running off an airport I was losing connections every period. My email wouldn't work. I couldn't use some of my favorite websites that I teach with, like Brainpop because the connection would be so weak, even though the airport was in my room. In order to get anything to work, I had to reboot my computer at least once a period, sometimes twice. And, yet again, I was putting in work orders to get a network cable run through the ceiling and dropped down to where I have to have my computer station because of the Model Classroom wiring. This time I actually had new tech reps who said it could be done, but it had to be done by an outside vendor and they'd put me on the list.
And then they'd close my work order saying the work was completed.
And no one ever came and fixed the problem.
So, I did another work order. And they'd close it. And another, and they'd close it. (See the pattern here?). One of them finally told me to stop doing the work orders because I was "on the list." I found out from Mrs. Talladega, who teaches our technology kids (groups of students who do some computer repairs and maintenance in the building and who, in my opinion, know quite a bit more than the tech reps actually hired by the District) that the reason they kept closing my work order was because they get in trouble when there's one there for more than 5 days. Considering I've been issuing work orders on this same problem since August of 06, I'm sure they weren't happy. Mrs. Talladega had seen all my work orders (she reviews them to see if we can solve it in-house or bump it up to District) and she was as frustrated with the situation as I was.
Finally, last week, I lost it. I couldn't show a Brainpop video for a review, I couldn't get my emails (was expecting one from a parent that was pretty important), and I had just had it. I sent Mrs. Talladega an email telling her to find a 40 foot network cord and I'd wire the damn thing myself.
The next morning I arrive at 6:15 to find the Guidance Goober (the biggest computer geek head I know) in my room, running an network cable through the ceiling for me.
"I got sick and tired of waiting for the Technology Department to do this, so I'm doing it myself, even though we aren't supposed to," he said. He had me hooked up and running by the time the kids rolled in that morning, and now I even have a phone on my desk (and not across the room). I have a good connection. I haven't had to reboot my computer a single time. I can show a Brainpop.
The Guidance Goober is a treasure. I know he's frustrated by the limitations we currently have with technology as we've both discussed blogging and wikis for the kids which is something we'd like to do in the future once we have the capability. He's actually testing out some things along these lines (on his own, mind you) and hopefully we'll be able to get something in place soon. Of course, my kids, as long as we don't have the Cisco routers which are supposed to solve all the world's problems, will still have the same connection issues I had with the airports, so I guess it's all a moot point until we can actually connect. It's frustrating.
Mrs. Talladega, The Guidance Goober, and I, however, have a little game going. We're placing bets on when the District tech people get to their "list" and actually come out to wire my room. I'm guessing April.