Learning

November 13, 2000

Today is the start

of the coldest week we’ve had since winter. It’s about 40 degrees in the morning

and 60 in the afternoon. I don’t know how to react. I’ve been working on the

coding for our ASP project. It’s almost done, I’ll just need to go into the

server room to update the intranet machine. I’ve focused on also finding a nice

job posting system, but that will be something later. The new intranet pages

are almost done. I am actually at a point where I have time to actually go out

with friends. 

My former co-worker

Doug has a new job at Georgia Tech, actually it’s a true geek job. He has a

damn SGI O2 on his desk . This seems like a job

where you come in wanting to learn and you actually do so. I was in that type

of environment for years, although not as advanced as Georgia Tech, and part

of my move to Marketing was to continue that learning. I learned more about

“legitimate” design here than all of the other years doing web stuff.

However, I learned more about computers while I was a 2nd shift operator (a.k.a

Tape Monkey) where I had the time to screw up a computer then figure out how

to fix it before the end of my day (around 11pm).

I was also around mentors

who guided/smacked around/pushed me to the “correct” ways to do things.

I worked with a guy who was an HP engineer for about 10 years and a Data General

tech for about the same amount. He was use to working on BIG machines that had

to be online now not and hour from now. I been on the phone with this

guy late at night trying to figure out why something wasn’t working, at one

point he had some medical problems that took him out of commission for about

a month and he would still call in to see if he could help. It was so inspiring

to call someone who could tell you how to fix a Novell server over the phone

without having the machine in front of him. He knew his network. Novell servers

were the beginning, I learned Terminal Servers from a short course about how

to do things, then I would telnet into one during 2nd shift to figure out what

did what. PCs were fun to learn, I learned so many ways to fix a system. It

was through the troubleshooting skills I learned in IS, that I could apply that

to anything. If something isn’t working, they plan B. I always have a Plan B

before I began Plan A. I wasn’t always in a place where I could ask for help,

I had to be a bulldog and get the damn thing fixed.

It use to kill me when people

would run back to me after their 1st attempt and say they couldn’t figure it

out. Then I figured out it was a confidence issue. I had to build their confidence

so they would try, that was exactly how I was handled when I started.