I am the IT guy at the school. In a small school this means a whole bunch of things are mine. Things like projectors, screens, sound systems and, worst of all, the bell system. I am the bell guy because the bells are rung by software. Scheduling software I am sure was originally written in the 70’s, by evil trolls with large painful bunions. A couple times a year I have to figure out how to use the software so I can change the bells for the new school year or fix holiday dates that have changed. This software is an excellent example of not-user-friendly. But it is good practice for my problem solving skills, which is a euphemism for “How in the heck does the %^$# software work?” The bells were not ringing in the elementary school after spring break. Of course the first thing I checked was the hardware. I push the button, the bells ring. Nuts, that means it is the scheduling software. Nuts again. I pull up the software. I am pretty sure this was originally written for DOS 1 beta. I email the company to find out if there was ever a manual written for the software. Nope. Bummer. (Who writes software with no manual?) I stare and tinker. An hour later I have an epiphany. “You’re kidding me. That’s how it works?!” I got it now. If I was clever (never one of my stronger features) I would write my own manual on how this misbegotten piece of trash works but I only have to monkey with it once a year so I will let the bunion ridden trolls call this a victory. All I care about is the bells are ringing and I do not have to deal with them for another year. Maybe.
One ringy-dingy, two ringy-dingy