Another successful fundraiser

Last night’s show was the last of three fundraising episodes for this fund drive. We were tasked with raising $1920 per show. To make the goal easier to speak to I just announced it as $2000 as a nice, round number.

During week 1 we raised nearly $2700 which was pretty awesome. Our listeners stepped up in a big way. We were joined by Renee Feltz of the KPFT News Department as the fund raising coordinator during the program. Her energy added greatly to the efforts.

During week 2 we fell short of the goal by about $500 so that was a little disappointing. Still, with the overage the first week we has some cushion and in terms of the overall goal we were right where we needed to be. Renee was out of town and Robb was absent as well. Dr. Simotas was our fundraiser coordinator and she did a good job. It was her first time to work with the Technology Bytes crew so it didn’t gel as well as I would have liked.

Last night we were re-joined by Renee Feltz and Robb Zipp in their usual roles and Dr. Simotas joined us in the studio. It was a winning line-up as we blew through the goal with 30 minutes left in the show. I think having a fully qualified ObGyn in the studio and on the air during a computer technology talk show pushed us over the edge. The final tally for last nights show was just over $2600.

Alexandra Simotas in the control room with phliKtid

Overall, we exceeded our goal and it was a successful fund drive for us.

Cult of the Mac – Finding love

So Apple computers has this interesting 24 hour time lapse movie on their site. The camera is in front of the 5th Ave store in New York. You can watch it here.

Pretty fascinating in a commercialized, Koyaanisqatsi sort of way.

There is a bit of an Easter Egg in there if you watch it, though.
If you watch the second 5:00 am segment you will see a young man hijack the cam to offer a marriage proposal. You can skip through and around the movie in 1 hour increments if you don’t want to watch the whole thing.

I love you

Will you marry me?

I didn’t get a frame grab of the card with her name on it…

Glad to be of assistance

As you might imagine, I have answered a LOT of computer questions over the years as a result of my chosen path as demagogy-free radio talk show host and newspaper techno-pundit.

The questions come via e-mail, IM, the phone, in person and via third parties, friends and relatives. Everything from consumer advice to complex network troubleshooting. Sometimes I know the answer and sometimes I am quick with a well executed Google search and on certain occasions I just grunt my displeasure at being used in this manner and go back to what I was doing before I was so rudely interrupted.

Since all my Q&A’s I write for the Chronicle are archived in the Helpline Blog they are turning up in the search engines when people are looking for an answer to a problem. This means that I am answering questions now without actually interacting with the person experiencing the problem.

There’s no way to track this. I simply have no idea how much assistance (or damage) I am perpetrating. I do, however, have an inkling based on the steady stream of replies to one particular posting I made back on Sept. 9, 2005.

My screen is sideways

It was a Q&A I put together based on a real live helpdesk issue that I solved with one of my users in the course of my workday. In terms of publishing it was kind of a “throw down” posting in that I did not see this as something that affected very many people and would possibly be more filler than anything or perhaps just demonstrate a quirky computer factoid.

I was wrong.

This week I have received three comments thanking me for that one single answer and I have received around 28 since it was posted. And since I rarely hear from people I have successfully helped the true number of people this has helped may never be fully known.

I can only imagine how many people have been suffering with a monitor turned on it’s side looking for a solution.

I’m glad I could help.

Code monkey like Fritos

Code Monkey get up get coffee
Code Monkey go to job
Code Monkey have boring meeting
With boring manager Rob
Rob say Code Monkey seem to work a lot
But his output stink
His code not “functional” or “elegant”
What do Code Monkey think?
Code Monkey think maybe manager want to write god damned login page himself
Code Monkey not say it out loud
Code Monkey not crazy, just proud.

Johnathon Coulton is writing, recording and posting a song a week as part of something called A Thing A Week. This offering is “Code Monkey” and it’s a delightful tribute to software programmers.

Also of note is his “Flickr” song. If you have ever browsed Flickr (or any other photo hosting site) you will appreciate this song/video.

Lastly, Chiron Beta Prime reminds me a LOT of They Might Be Giants.

Thing A Week is available as a Podcast if you are so inclined.

Google-spike

I’m enjoying this while it’s still novel.

Today’s Helpline Blog item was a Q&A about Mozilla Firefox and Internet Explorer entitled Trying to eliminate Internet Explorer. Apparently Google News bundled this blog entry with the news release regarding Microsoft’s release of Internet Explorer Beta 7.

This resulted in ginormous spike in the number of page views in less than 20-30 minutes and an explosion of comments that I am slowly but surely reviewing and publishing.

Forgive an old man his dated colloquialism but I have to say one thing….

NEAT!

from border to border and coast to coast and all the ships at sea

Technology Bytes is moving back to it’s old time slot of 8-10 pm. We had been moved to the 7-9 pm slot for awhile but it was just not the same so I lobbied for our old slot and they finally gave it to us. The change takes effect Wednesday April 19th.

This is part of a station-wide programming revamp. Many shows are moving. The new program schedule is online at the KPFT website and can be downloaded in PDF format directly from this link.

In other Tech Bytes house-keeping news; Groovehouse has been doing an awesome job as the new phone screener, following in the footsteps of the original Phone Girl, Leslie the Phone Girl, Phone Boy and David. And beyond that he has become the official photo-chronicler of Tech Bytes at the studio and at our events. You can check out his work in the on-air gallery of geekradio.com.

Some of my favorites:

Jay Lee, Barrett Canon, Lauren Steffy, Dwight Silverman Jay Lee and Barrett Canon Phlikitid in the control room

Request for help gone horribly wrong

.

After my post about how to deal with IT people when seeking assistance one of my readers provided me with the following story from The Register.

Oklahoma city threatens to call FBI over ‘renegade’ Linux maker
Follow the link and scroll to the bottom to read the related stories.

The heartland turned vicious this week when an Oklahoma town threatened to call in the FBI because its web site was hacked by Linux maker Cent OS. Problem is CentOS didn’t hack Tuttle’s web site at all. The city’s hosting provider had simply botched a web server.

This tale kicked off yesterday when Tuttle’s city manager Jerry Taylor fired off an angry message to the CentOS staff. Taylor had popped onto the city’s web site and found the standard Apache server configuration boilerplate that appears with a new web server installation. Taylor seemed to confuse this with a potential hack attack on the bustling town’s IT infrastructure.

“Who gave you permission to invade my website and block me and anyone else from accessing it???,” Taylor wrote to CentOS. “Please remove your software immediately before I report it to government officials!! I am the City Manager of Tuttle, Oklahoma.”

Few people would initiate a tech support query like this, but these are dangerous times, and Taylor suspected the worst. (Er, but only the world’s most boring hacker would break into a site and then throw up a boilerplate about how to fix the hack.)

CentOS developer Johnny Hughes jumped on the case and tried to explain the situation to Taylor.

“I feel sorry for your city,” he replied in an e-mail. “CentOS is an operating system. It is probably installed on the computer that runs your website. . . . Please contact someone who does IT for you and show them the page so that they can configure your apache webserver correctly.”

That response didn’t go over so well.

“Get this web site off my home page!!!!! It is blocking access to my website!!!!~!,” Taylor responded, clearly excited about the situation and sensing that Bin Laden was near.

Again, CentOS jumped in to try and explain some of the technical details behind the problem. It pointed Taylor to this page, saying it was the standard page for a web server and noted that it provides instructions on how to fix the problem. The CentOS staffer suggested that Taylor contact his service provider or have an administrator look into the issue.

That response didn’t go over so well.

“Unless this software is removed I will file a complaint with the FBI,” Taylor replied.

Later he added,

“I have four computers located at City Hall. All of these computers display the same CentOS page when attempting to bring up Tuttle-ok.gov. Now if your software is not causing this problem, how does it happen??? No one outside this building has complained about this problem. This is a block of public access to a city’s website. Remove your software within the next 12 hours or an official complaint to the FBI is being filed!”

And later,

“I am computer literate! I have 22 years in computer systems engineering and operation. Now, can you tell me how to remove ‘your software’ that you acknowledge you provided free of charge? I consider this ‘hacking.'”

After a few more exciting exchanges, CentOS managed to track down the problem for Taylor. It turns out that hosting provider Vidia Communications is running CentOS on some of its servers and had not configured the Tuttle web site properly. CentOS informed Taylor of the situation, and, a day later, Taylor had calmed down.

“The problem has been resolved by VIDIA who used to host the City website,” he wrote. “They still provide cable service but do not host the website. The explanation was that they had a crash and during the rebuild they reinstalled the software that affected our website.”

“I am sorry that we had to go through the process and accusations to get the problem resolved. It could have been resolved a lot quicker if the initial correspondence with you provided the helpful information that was transmitted in the last messages. My initial contact with VIDIA disallowed any knowledge of creating the problem.”

Er, so despite the fact that CentOS went out of its way to figure out the problem for Tuttle, Taylor still places the blame on CentOS for not fixing the problem – that it didn’t create – sooner. In addition, Taylor didn’t really start off the whole process on the best foot despite Tuttle being a town “Where People Grow – Friendly!” Grow friendly, threaten to bring in the FBI at the drop of a hat – what’s the difference?

Dealing with your IT professional

There’s a lot of focus these days on customer service. And while it’s true that the service professional is responsible for his role in any customer service interaction, there are things that the customer can do to help facilitate a positive experience.

With that in mind, I offer these tips for dealing with your IT dept.

1. REBOOT YOUR COMPUTER

If you have not rebooted your PC to see if it clears up the problem you have done nothing. Many problems can be cleared up with a simple restart of your computer. If it’s locked up, force it to turn off by pulling the power if necessary.

When you call the helpdesk one of the first questions you are likely to be asked is “Did you reboot?” If you answer yes then you move on to phase 2 of the troubleshooting process. If you answer “No” you may be sent away to do so and have to get back into the queue for support.

Also keep in mind that just because you don’t see how a reboot could solve the problem does not mean it’s not a good thing to try. When it comes to asking for help with your computer, your understanding of the troubleshooting process is not essential to getting your problem resolved. I know it sounds harsh, but it’s true. When you call the helpdesk and you indicate you have already tried rebooting your computer the technician is likely to respond favorably to you and the rest of the troubleshooting process is likely to be way more pleasant.

It’s also quite likely that the reboot will make the call the to the helpdesk completely unnecessary and then EVERYBODY wins.

2. DON’T LIE

Your IT professional may ask you questions in the diagnosis process.
For example, the IT person may ask “Did you change anything?” to which most people reply “No, I didn’t change anything.”

Installing software programs counts as change.
Installing a security patch counts as change.
Adding or removing hardware components counts as change.
For the more painfully literal IT people the fact that you observed your computer running counts as change if you apply the Schrödinger’s Cat mental exercise. I pity you if you are cursed with such a technician.

Another common user lie is “I tried everything.” Obviously you DIDN’T try everything, or you wouldn’t be seeking help and you would have solved the problem yourself.

Speaking of trying things, if you are able to remember what you tried this can help the technician figure out how much worse you have made the original problem and guide them through the process undoing the additional damage caused by attempting to fix the problem yourself.

3. ASK GOOD QUESTIONS

Let’s say you arrive at work, turn on your computer and are unable to get to e-mail, you’re stock reports (which you shouldn’t be doing on company time, tsk tsk!) or communicate with your friends via AIM, Yahoo or whatever (again, TSK TSK!)

This first instinct of most users is to contact the helpdesk and ask “Is the Internet down?” to which the technician will usually respond to by saying “No.” This is because the Internet is not likely going to be completely down but since you asked, they answered. A good technician knows what you are really asking but is often so painfully literal that they will answer the question asked rather than try to determine what you really need.

A better way to approach this problem would be to say something along the lines of “I can’t seem to connect to the Internet, is there a network problem?” to which the answer may still be “No” but this will facilitate the process of determining why YOU cannot connect to the Internet.

4. DON’T OFFER USELESS INFORMATION

A common comment technicians hear is the phrase “It worked yesterday” or “It was working fine up until I got back from lunch.”

Well, duh. That’s what we in the business call BROKEN. The fact that something functioned before is not a guarantee it will work in the future. We know it worked fine before, that’s why we have not heard from you until now.

Just state the problem concisely. “My computer will not start” or “I’m being bombarded by porn pop-ups.”

We know your computer started yesterday and that you were pop-up free up until you cruised that non-work related web site during your lunch hour.

It’s not important and will not get your problem solved any faster.

You should also try to minimize guessing what you think the problem might be once the diagnosis has begun. Let the technician do his work.

Also, while technicians appreciate users being contrite and self effacing, you could exacerbate your problem if you subject your technician to the phrase “I’m computer illiterate” or “I know just enough to be dangerous.” It’s like those morons in the Renaissance Festival parade who go by saying “Smile and wave” not realizing that the poor patron standing there is going to have to hear that bit of cleverness from the next 50 parade participants marching by.

Say something meaningful like “I appreciate you taking the time to help me” and “Thanks.”

5. RESPECT YOU TECH’S PERSONAL TIME

In the course of the day you might see one of your IT people walking about. They are usually not just wandering aimlessly looking for someone to ask them a question. Chances are they are on their way to work on another problem or they are on a break. They might even be done for the day.

When you see one of your IT people walking by and you stop them and say “Quick question” you need to know that all questions are quick.

“What is the airspeed of an unladen swallow?” is a quick question. What takes time is determining whether you mean an African Swallow or a European Swallow and details such as wind speed, air pressure, elevation and so forth. There simply is not enough time to answer your question before the elevator doors open or before it’s time to flush and wash up.

You should also keep in mind that if you flag down an IT person on the floor and ask them for something that can’t be done immediately they are going to forget in the time it takes them to make their way back to their desk. This is because they are probably going to be stopped a dozen more times and asked a “quick question” before they make it. If you need something from IT follow the procedure and submit a ticket or send an e-mail.

Besides, the problem you are having almost certainly existed before you saw the tech walk by and the fact that you have not contacted the helpdesk already would tend to indicate that the matter is not urgent.

These simple suggestions can go a long way toward endearing yourself to your IT department and can mean the difference between good tech support and excellent tech support.