Yeah, we had a tech support team in my previous company. And, all things told, they did a pretty good job. I miss that now.
Thu May 20 2010 07:15:50 PM EDT from Peter Pulse @ UncensoredWhere I am now, they have a whole department just for that.
Ah, the joys of being accused of being a spammer. That's always fun.
The only thing worse than actual spammers are antispam vigilantes, especially when they can't distinguish real spam from something they actually signed up for. At my job I occasionally find myself having to contend with one of these morons. One of them was so obstinate that she actually tracked down my home phone number and started harassing my family.
My usual policy is to put their email addresses on a web page from which real spammers can harvest them. :)
just put it in a debian bureport.
I got 4 hours of training to do a no mistake job : space dye. Usual SNAFU stuff. I get to see Monday if the stuff I did Friday is any good.
(Heh. Post photos if it comes out well. That sounds cool.)
I used to do that job, sort of. I had pretty much no technical know-how. I knew how the program worked. Someone would tell me they had a problem. I'd take down the info, try to re-create the problem, find the programmer who handled that part of the program, show them the issue, ask what to do, reply to the customer. It was a system that could drive a lot of people crazy, but it worked for a number of reasons. 1. Only I bugged the programmers as opposed to customers. 2. The customers were English speakers and the programmers weren't. 3. Since most problems are recurring, once I'd dealt with it once, I would leave the programmers alone about that problem thereafter.
I did it as a student making about 1.5x minimum wage.
Just a thought.
Sorry, no cameras allowed there. But I'll tell you where to buy it. Look at the thread in your local Wal Mart supercenter. It should have something that's multi-colored. We are doing something for the seats in railroad cars, so commuters on the LIRR will not wear out the seats having sex. I did ask my rocket scientist relative about using some stuff on Mars proposals.
jock, what are you talking about ever?
Where I am now, they have a whole department just for that.
My first job was like that. ahhh the good old days.
So they're penalizing the good guys.
The level of stupidity sometimes. These people should have their computers taken away from them.
A friend of mine told me a long time ago that your boss and coworkers don't want to hear "no" as an answer to a request to do something. It took me a while to completely understand what he was saying, but I do now and try to practice it when I can.
Instead of saying, "No, I can't do that," rather say that you can, but explain the consequences. For example, I maintain a number of automated test beds here at work. We have similar test beds at different sites around the world.
Every so often I get asked, "Why don't you maintain those test beds, too?" or "Could you take a look at this problem with this remote test bed?" My typical answer is, "Sure, I can take a look at that, but I only have remote access, so I'm limited in what I can do. It may take some extra time, and if it takes too much time, I'll need to clear it with my boss otherwise I may compromise my schedule." Usually, that will get the requestor to change their mind and retract their request.
do you run something like buildot and such?
What is buildot?
its actualy buildbot
its python/twisted, and can run compiles & unit tests plus can be triggered by post commit hooks...
bart: I'll have to look into that. The systems I maintain are geared for functional, systems, and performance testing, not unit testing, but I know our developers are always looking for way to improve their unit testing.
its primarily for running stuff over and over and display a 'successfull executed' - or not and display that.
"The customer is reporting the box as dead on arrival. He can't start it up. I know you're taking vacation next week, so I need a set of instructions for making a new box."
Not likely. I can't remember how to build any of our boxes anymore. I fly by the seat of my pants, because our rate of change outstrips my ability to keep anything documented, or to prepare appropriate scripts for creating anything new.
I suggested he just replace the parts that are broken and leave the hard-drives alone.