the goal for "break"
First off, I'm a 12-month employee at an educational institution. Additionally, most people prefer that I do much of my job when they aren't working. Therefore, I get a little touchy about this whole notion of the "break". I don't mind working hard, even heinously long hours, while students and instructors are gone. (Actually, I really like working at an educational institution when there aren't students and faculty hanging around trying to do stuff. Or staff and administrators, but that's not usually a problem.) What I mind is the assumption that I have been somewhere else, even on a vacation. The nerve.
I will be bringing up a new satellite campus; 5 classrooms, 1 w/ 30 laptops, a couple of offices, a file server and a few domain controllers (virtualized), a few wireless access points. The tricky part is that it will be a pilot for a few new technologies; a wireless controller w/ the AP's running a lightweight OS, multiple SSID's of differing security levels & requiring different network routing, and most of all we will implement VoIP. That's Voice over IP. It's not skype, it's business class voice requirements and tying it in with the behemoth ROLM system. Of course, I'll have a number of smaller projects to fit into January, too.
That shouldn't be here nor there, but it does suck my brains out before I get home. What I really want to get done is the scripting of the instructional units, podcast recording, make all
of my slides and assemble them into enhanced podcasts. That's a non-trivial amount of work but I'm pretty comfortable w/ the content. I want to try to work in a technique of calculating binary bytes on the fingers. I've never seen it taught, but it's something that evolved for me along with my understanding. I've heard of a few other people who did that but never spoke to anyone about it. I certainly never tried to teach it. That's a bit bold but could be bery powerful.
The central point that I've come to realize is that I am focused primarily on the instructional aspect of this project. I'm very attached to the effectiveness of the instruction. I am interested in the technological aspect, but really only insofar as it serves learning. I am emphatically uninterested in a repackaging of a run-of-the-mill product.
It would be cool if I get a real plan for the skill modules functionality down on paper (as it were). Building the website would certainly give me a leg up. Getting the actual requirements of the standard format that has been alluded to would certainly be helpful. But my focus is on getting the actual content done. I got some feedback that there was poor sound in the left channel, detectable on earphones. I didn't hear it on the computer, but I thought I saw something like that on the monitor. I didn't pursue it because the two recorded channel patterns I saw in Garage Band matched. I whined about a reduced level on the new mic to my Apple rep and he asked about the 9-volt that powers the mic. I said it was new, but when I looked at the other one of the two that my friend gave me, I saw the bottom bulging out. I had tossed them both into the front pocket of my hoodie and, once I got home to take them out, they were very hot. I laughed at the time, but I'm hoping the source of the sound problem is as simple as new 9-volt EveryReady's.
That's my goal(s).
I will be bringing up a new satellite campus; 5 classrooms, 1 w/ 30 laptops, a couple of offices, a file server and a few domain controllers (virtualized), a few wireless access points. The tricky part is that it will be a pilot for a few new technologies; a wireless controller w/ the AP's running a lightweight OS, multiple SSID's of differing security levels & requiring different network routing, and most of all we will implement VoIP. That's Voice over IP. It's not skype, it's business class voice requirements and tying it in with the behemoth ROLM system. Of course, I'll have a number of smaller projects to fit into January, too.
That shouldn't be here nor there, but it does suck my brains out before I get home. What I really want to get done is the scripting of the instructional units, podcast recording, make all
of my slides and assemble them into enhanced podcasts. That's a non-trivial amount of work but I'm pretty comfortable w/ the content. I want to try to work in a technique of calculating binary bytes on the fingers. I've never seen it taught, but it's something that evolved for me along with my understanding. I've heard of a few other people who did that but never spoke to anyone about it. I certainly never tried to teach it. That's a bit bold but could be bery powerful.The central point that I've come to realize is that I am focused primarily on the instructional aspect of this project. I'm very attached to the effectiveness of the instruction. I am interested in the technological aspect, but really only insofar as it serves learning. I am emphatically uninterested in a repackaging of a run-of-the-mill product.
It would be cool if I get a real plan for the skill modules functionality down on paper (as it were). Building the website would certainly give me a leg up. Getting the actual requirements of the standard format that has been alluded to would certainly be helpful. But my focus is on getting the actual content done. I got some feedback that there was poor sound in the left channel, detectable on earphones. I didn't hear it on the computer, but I thought I saw something like that on the monitor. I didn't pursue it because the two recorded channel patterns I saw in Garage Band matched. I whined about a reduced level on the new mic to my Apple rep and he asked about the 9-volt that powers the mic. I said it was new, but when I looked at the other one of the two that my friend gave me, I saw the bottom bulging out. I had tossed them both into the front pocket of my hoodie and, once I got home to take them out, they were very hot. I laughed at the time, but I'm hoping the source of the sound problem is as simple as new 9-volt EveryReady's.
That's my goal(s).
posted by Mikki Adams at 5:08 AM
0 Comments:
Post a Comment
<< Home