Friday, June 20, 2003
I don't know how I want to feel about this. There's computer people here in the office, doing things with our systems. That's kinda, sorta, supposed to be my job. It had to be neglected in favor of more important stuff. Clarence needed to be migrated to a new system, at the other shop, and I just never found enough time to really deal with the situation. Now we have techies in here doing stuff and I have a vague sense of having my 'turf' invaded. Not that I have time to deal with it anyway. I'm behind on at least two other things and I probably won't be here next week. There just isn't time for me to do this project. Still, I can't shake the feeling that interlopers are prying into my business.
Toodles.
Toodles.
Thursday, June 19, 2003
Wednesday, June 18, 2003
I had a good day. I worked hard since first thing this morning and I managed to get two things done, that I wanted to get out today. I'm not really at the end of all the things I need to get done, but I set a goal, and managed to complete it. Its been awhile since I was able to do that. It feels pretty good.
Toodles!
Toodles!
Tuesday, June 17, 2003
Sorry for not doing a more in-depth entry for today. I got a call this morning asking where the quote that had been requested a couple of weeks ago, was. I'd filed it to do later, then not gotten back to it. So I went, flat out, all day, finishing it. I should have read the thing more closely before filing it. At the end of the second page was a deadline. Just another example of there being too much to do, and not enough time to do it all in. Much like forgetting to write in the blog. Both things got done though, so I can't feel too bad.
Toodles!
Toodles!
Monday, June 16, 2003
I have a question. Actually, its more of a complaint than a question but its phrased in the form of a question.
Why is it no one has ever DONE anything when a computer breaks. I don't get that. I'm supposed to fix something, not replace it, or redo it, I'm supposed to 'fix' it, and not lose any data. But the person in question has not 'done' anything to cause the machine ti stop operating correctly. It just broke itself.
This drives me up the wall. Obviously something happened to make it stop working right. Nothing, anywhere, breaks completely mysteriously, without cause of provocation. There is always a cause and if you can ascertain when it started happening, maybe you can figure out the why. But no one wants to tell you what lead up to the failure. More likely than not they were mucking with something they shouldn't have, and now it doesn't work right. If they tell you what it was they were doing, maybe you can put it back and it will work. When its 'just broken' I'm at a loss about how to get it back to right. My theory is to just nuke it and start over, and be damned that they haven't been backing up their data.
That's just my two cents though.
Toodles.
Why is it no one has ever DONE anything when a computer breaks. I don't get that. I'm supposed to fix something, not replace it, or redo it, I'm supposed to 'fix' it, and not lose any data. But the person in question has not 'done' anything to cause the machine ti stop operating correctly. It just broke itself.
This drives me up the wall. Obviously something happened to make it stop working right. Nothing, anywhere, breaks completely mysteriously, without cause of provocation. There is always a cause and if you can ascertain when it started happening, maybe you can figure out the why. But no one wants to tell you what lead up to the failure. More likely than not they were mucking with something they shouldn't have, and now it doesn't work right. If they tell you what it was they were doing, maybe you can put it back and it will work. When its 'just broken' I'm at a loss about how to get it back to right. My theory is to just nuke it and start over, and be damned that they haven't been backing up their data.
That's just my two cents though.
Toodles.