Web Site vs. Blog

What’s the Difference?

Today I got a phone call from our local newspaper’s “business advocate” — the guy who writes stories about business. He was researching an article about blogging and figured that I was the most active blogger — if not the only blogger — in town, so I might be able to to provide some information about it. He wasn’t aware that I’d co-authored a book about WordPress blogging software (WordPress 2: Visual QuickStart Guide) in 2006 and he probably wasn’t aware that I wrote Putting Your Small Business on the Web back in 2000. He probably also doesn’t know that I’ve written four books about Web authoring software (various versions of PageMill, now defunct) and that I’ve been building and managing Web sites since 1994 (although I’m not crazy enough to do it for a living).

We stumbled a bit in our conversation. He referred to my Web site, wickenburg-az.com, as a blog. (The site has been around since 1999, predating the blogging phenomena by at least 3 to 4 years.) I responded that it wasn’t a blog, that it was a Web site built with blogging software. And then he asked me what the difference was.

I had to think about it. What is the difference between a Web site and a blog?

They’re very much alike.

Let’s take a look at the similarities.

  • Web sites and blogs are both published on the Web and can be read with any Web browser. This gives them the same basic look and feel and similar user experiences. Web sites built with blogging software can look and feel just like a blog, even if that’s not what they are intended to be.
  • They depend on good, useful content. Web site visitors and blog readers come to read content. If the content is good and meets their needs, they’ll be back for more. If the content sucks, they won’t.

But they are different.

Of course, I needed to explain how they were different — not how they were the same. The response I came up with centered around the purpose of visitors coming to to the site, but there are more differences.

  • Web site visitors come to a site to look for specific information. That information does not need to be new. It just needs to be what the visitor is looking for. For example, I visit the HP Web site when I need a new driver for one of my printers. I know it’ll be there and I don’t care if it’s been there for five years. People visit wickenburg-az.com to get basic information about Wickenburg: what it’s like, what to do there, etc. But blog readers visit or subscribe to blogs to get fresh information or insight on topics that are important to them. I read ProBlogger, for example, because it has timely articles that can help me understand how to be a better blogger. People visit aneclecticmind.com to read articles like this one about blogging, or other articles about flying, or even other articles about what it’s like to live in a place like Wickenburg — all from my point of view.
  • Blogs tend to be more opinion-based than Web sites. Sure, HP is going to tell you on their Web site that their printers are the best, but what would you expect? On my blog, I’ll tell you what I think about my HP printer and compare it to other printers I might own or have experience with. I’ll also tell you what I think of Apple Geniuses or local restaurants or life revolving around the Internet. (Although some locals might find this hard to believe, I keep most of my negative opinions of Wickenburg out of wickenburg-az.com. Most.) The opinion aspect makes blogs more personal than a Web site.
  • Blogs rely on fresh content. It’s commonly accepted that a blogger should post at least 3 to 5 new entries a week. Web sites, on the other hand, are more static and don’t require as much updating. Their visitors don’t expect it, either.

Does it matter?

Who knows? But it’s made me think about blogging a bit more than usual lately. And I’m sure it will lead to a few more articles here about what makes a blog a blog in the near future.

iPod Microphones: A Review

On the Future Tense Podcast.

One of the other podcasts I really enjoy is American Public Media’s Future Tense. This public radio show has 3 to 5 minute segments on topics related to computing and technology. I highly recommend it for a quick dose of what’s new presented in plain English.

XtremeMac IPV-MIC-00 MicroMemo Digital Voice Recorder for iPod Video (Black)For those of you interested in recording with your iPod, the February 12 episode, iPod Microphones: a Review, should make good listening. It certainly pleased me. It confirmed that the iPod microphone I recently purchased — the XtremeMac MicroMemo — was the best of the three reviewed. The podcast also includes sample recordings with various mics under various conditions to give you an idea of what to expect if you invest in one of these gadgets for your iPod.

Penn Radio Podcast

No bullsh*t.

Penn Gillette, the bigger and louder half or the Penn & Teller magic team, is the kind of guy that you either love or hate. He’s loud and he can definitely be obnoxious. But, like me, he has a zero-tolerance stand on bull.

I subscribe to the Penn Radio Podcast. I listen to about half the episodes. It’s usually just a talk show with Penn and his sidekick, Michael Goudeau, talking about a topic in the news and people calling in. Some of the callers are good, others are clearly wacko. Talk radio at its best.

I agree with a lot — but not all — of what Penn has to say, especially about religion and politics. You might think that’s scary. I know my mother would. (Let’s not tell her, okay?)

Once in a while, they have a guest. Penn and the guest, with a little input from Michael, chat about things. Informative, entertaining, enlightening. Usually something to think about.

Flim-Flam! Psychics, ESP, Unicorns, and Other DelusionsEvery once in a while, Penn has a better than average guest. (Phyllis Diller was one of them months ago.) I just finished listening to his February 9 show, which featured James Randi, a skeptic who has devoted much of his life to exposing fraudulent psychics, claims of ESP, and other “new age phenomena.” In other words, bullsh*t. He even wrote a book about it: Flim-Flam! Psychics, ESP, Unicorns, and Other Delusions. The radio show was an interesting look at the tricks today’s top psychics use to give “readings” as well as insight into people who really believe they have these powers.

Anyway, if the topic interests you, you might want to download the podcast episode and give it a listen. Use the Comments link to let me know what you think about it.

And please try to keep Randi-bashing comments to yourself. I just read enough of them on Amazon.com.

A Search…

…but no rescue required.

I was sitting down at my desk, getting ready to start working on Chapter 6 of my Excel 2007 book (for the third time), when my phone rang. It was someone I knew from here in Wickenburg. He was wondering if I was available for a helicopter flight that day. It seemed that his son and his wife and young child had gone hiking and hadn’t come back.

Jeez!

Yes, I was available. I asked a bunch of questions, like whether the authorities were involved. He told me the police knew but hadn’t started looking yet. But he wanted to start looking right away. He thought they might be in the Granite Mountain area. That’s near Prescott, about 40 NM away.

I warned him that it could be expensive to search by helicopter. He said he didn’t care. I told him I could have the helicopter ready to fly in 30 minutes. I told him to give me a call if he wanted to go out. And we hung up.

He called back ten minutes later, just when I was warming up my Dell PC. He would meet me at the airport.

I dropped everything, threw on some jeans and practical shoes, grabbed my handheld GPS to track our search area, hopped in my Jeep, and drove off to the airport.

His mom, who I already knew, arrived at the airport as I was pulling the helicopter to the fuel island. I talked with her after I fueled up. Weather was closing in — an unusual thing here in Arizona — and the ceilings were dropping. Rain was a certainty. And to the north, where I needed to fly, the tops of the mountains were obscured by clouds. I’d checked the weather by computer before leaving home and things in Prescott looked okay for at least the next two hours. But I wanted to get up there as soon as possible.

Doug and his wife arrived a short while later. I gave them a preflight briefing, loaded them on board, and attempted to start the helicopter. For the first time ever, it took five tries to start. I’d flooded the engine while priming it.

We crossed the Weaver Mountains north of Wickenburg to the east northwest of Yarnell. We were flying right below cloud level up there. But ahead, at Granite Mountain, the sky was only partly cloudy.

We reached the mountain 20 minutes after leaving Wickenburg. It’s a one-hour drive. We circled around the west side to the north, had some trouble getting permission from Prescott tower to skirt their airspace as we flew around the mountain, and then started looking for the missing people’s truck.

Of course, there are a few things that made this a less-than-perfect search. First and foremost is that they weren’t sure that the missing people had come to Granite Mountain. They might have gone to some trail that ran from I-17 to the Verde River — which was at least 40 miles away. Second, the wind was howling up at Prescott, with gust spreads of 10 miles per hour or more. As the wind came over the arms of Granite Mountain, it bounced us around something fierce. Doug was getting airsick. My barf bags were under his seat.

We did a good amount of searching, but with thoughts of puke on my leather seats, I suggested we land at the airport and check in with other people who were monitoring the phones. I don’t think Doug was happy, but he didn’t argue. Five minutes later, we were on the ramp at Prescott airport, near the terminal and restaurant, and Doug was heading toward the buildings while I shut down.

In the restaurant, while Doug drank Sprite and his wife and I enjoyed other beverages, Doug checked in. The missing people’s truck had been found. At the Cave Creek trailhead, wherever that was. He didn’t get the coordinates. We hurried back to the helicopter, started up, and headed south.

The weather to the south wasn’t good. We hit rain right away. I joked about how the rain took the bugs off the main rotor blades. I didn’t mention that it also took the paint off.

It was a good 20-minute flight down the east side of the Bradshaw Mountains, which were completely socked in. It was really beautiful, seeing those clouds mingling with the mountains. You have to understand — clouds are not a usual feature here in Arizona. And when there are so many and they’re layered among the mountains, it’s really a sight to see.

Past Black Canyon City, I headed southeast, hoping to hook up with the road that runs from Cave Creek/Carefree to the lakes on the Verde River. That’s where Doug thought the trailhead might be. The wind was blowing, the rain was falling. And then I caught sight of a DPS (Department of Public Services) helicopter flying northbound. I tuned into the helicopter air-to-air frequency (123.025) and made a call.

“Police Helicopter north of Cave Creek, are you on one-two-three-point-two?”

“This is Ranger 42, north of Cave Creek.”

I told him who I was and who I had on board. I asked if he was searching for the missing people. He said he was and that he was heading toward the trailhead where their car had been found. He offered to give me the coordinates. I told him we’d just follow him.

Now keep in mind that I was flying a Robinson R44 helicopter. He was flying something else, something turbine with lots of rotor blades. I don’t know what it was. But I took off after him and tried like hell to keep up. We lost sight of him three times among the mountains we were crossing, but we finally caught sight of him in a low orbit around a parking area. The missing people’s truck was parked down there.

Ranger 42 told us he’d search to the west and suggested we take the east. Okay with us. So we followed a few roads in the area for about 15 minutes. Then we heard the media helicopters coming in. Channel 3 with Scott at the controls. Channel 10. Channel 15? I don’t know. All I know is that they were coming. And no matter how big the sky was, it would be a lot smaller with three more helicopters.

Doug suggested that I land in the parking area, let him off, and let his nephew, who had found the truck, on board. Then he proceeded to puke repeatedly into the barf bags I’d had the foresight to remove from under his seat before we left Prescott. In the back, his wife was fine.

We landed. Doug got out. His nephew climbed in. I gave him a safety briefing, made sure he fastened his seat belt, told him not to get sick because we were out of barf bags, and took off.

We spent the next 30 minutes searching to the northeast of the parking area. Ranger 42 and two other helicopters that had shown up had landed to coordinate the search efforts. They graciously offered to leave room down in the parking area for me, but I preferred to stay out of their way. So we followed trails and roads up and down mountains and canyons.

After searching to the east, we crossed over and went west. I watched my fuel levels. I had about 1/4 tanks when we got back to the landing zone and found one of the police helicopters spinning up. I reported in.

“Ranger 42 is departing the area,” the pilot told me. “The missing people have been found.”

The missing guy’s mom, who was sitting behind me, was thrilled. We listened to the media helicopters talking to the police helicopters. It seems they’d gotten lost the evening before just as it was getting dark and had simply pitched a tent and spent the night in it. In the morning, they’d stumbled upon someone’s home and the woman who had lived there had driven them back to the parking area. Found.

Approaching the landing zone from the north, I watched the three helicopters there take off. I lined up for landing and settled down in the space they’d just vacated. My two passengers got out. I caught sight of a restroom in the parking area and decided to make use of it. Two minutes later, the engine was shut down and the blades were stopped and I was making a beeline for the toilet.

There were cops all over the place down there. One of them had approached me as I was shutting down and I said, “Please don’t give me a ticket.” After all, I’d landed in a parking lot for a trailhead. He laughed.

Everything was okay. Happy ending. Doug decided to drive back with someone else. I think he had enough of the helicopter. But his wife stuck with me. We climbed back on board, started the engine, and took off. The media helicopters were circling above us like vultures. I just followed the canyon south, climbing up out of their way while they jockeyed for position to land and interview the found people.

I headed southwest toward Deer Valley. I needed fuel to make it back to Wickenburg. But I hit a wall of rain that was just falling too hard for me to fly through with a passenger on board. I turned around and headed east. Things were clearer over the Verde River. When I cleared the canyon, I was able to turn back to the southwest.

The media helicopters weren’t far behind me. I heard them debate whether or not I had the found people on board with me. Apparently, the vehicles in the landing zone had driven off just as the first helicopter landed there. Doug’s wife and I had a good laugh.

We landed at Deer Valley and I arranged for fuel. Once fueled up, we took off to the northwest to return to Wickenburg. It was raining most of the way and we skirted below the clouds almost all the way to Wickenburg.

I showed my passenger her house from the air before we landed.

Time logged, 2.9 hours. And yes, I was paid for my time.

On Geniuses

Why I don’t Genius Bar hop and other comments regarding my recent hard disk problem.

One of my jobs as a blogger is to produce at least one blog entry a week. As you may have noticed if you follow this blog, it looks like I’ve been slacking off lately. Well, I just want to take a few moments to assert that looks may be deceiving.

Last week was a busy one for me. I finally got my computer back up and running after its second hard disk crash in a year. This crash was far more serious than the last and required the geniuses at the Apple Store to fix.

Now I know that lots of Mac pros laugh at the word “genius” when applied to the Apple Store’s tech support folks. And I do agree that it would be difficult to call any of them geniuses in the true sense of the word. (Think Einstein.) But if you were to compare their computer skills to the average Mac user’s, they could indeed be considered geniuses. They know a lot more about the current computer models than 95% of Mac users. Sadly, I fit into that 95% these days. I could tell you all kinds of things about fixing a Mac II cx or a PowerMac 7100/66 — and that’s because I used to teach a course about troubleshooting those computers running System 7. Nowadays, my troubleshooting capabilities are limited to what I need to know — like much of my other knowledge — and I don’t really need to know all the things the geniuses need to know to do their daily fix-it jobs.

So I’m not uncomfortable applying the word genius to many (but not all) of them. To me, some of them really are geniuses when it comes to diagnosing and fixing Mac problems.

I’ll also be the first to say that the capabilities of an Apple Store genius staff on any given day for any given store is hit or miss. It all depends on each staffer’s experience, knowledge, and interest in the topics he or she needs to know. I was at the Genius Bar in the Chandler, AZ store on Monday and the geniuses that day were pretty good. One of them was a super genius, the one who helped me was definitely above average, and the guy working the iPod slot was about average. (Let’s face it: it doesn’t take much skill to fix an iPod problem. Every iPod should come with a cheat sheet printed on back that explains how to reset it; that will resolve 95% of an iPod’s problems. The iPod guy probably resets a lot of iPods in a day. I’ve gotten so good at it that I can reset mine with one hand while flying my helicopter. Darn vibrations lock it up more often than I’d like to admit.)

I’ve had repeatedly bad luck at the Biltmore Apple Store in Phoenix, which is at least 30 miles closer to my house. The two times I tried to get assistance there, the lead Genius didn’t seem interested in looking deeply into my problem and didn’t seem to care whether it was resolved or not. On my fried motherboard problem, it seemed that she spent more time telling me how much it would cost to fix the problem than diagnosing what the problem was. This, coupled with her obvious lack of sympathy, made me doubt her diagnosis, so I had to go to another store (Chandler) to get a second opinion. I got a bad taste in my mouth (so to speak) from the experience. And that’s why I don’t go to the Biltmore store anymore.

Oddly enough, sympathy for my problem seems to be important to me. My main work computer or “production” machine (currently a Dual G5) is like a partner to me. It holds onto the projects I’m working on, it has the tools I need to get the job done as smoothly as possible. When it works right, we’re a team getting the job done. When it starts acting up, I get concerned. It’s not just a machine on the fritz. It’s a work partner feeling ill. What’s the problem? Can I fix it before it becomes critical? Is its motherboard about to go (again)? Or its hard disk? Will I lose data? Will I need to take it to the hospital (fix-it place) to get it working right again? How long will we be apart? And, of course, the selfish questions, like how long will I be unable to work?

The geniuses at the Chandler store are always sympathetic to my problem. They understand that my computer isn’t just a machine I use for e-mail and to surf the Web. They understand that its hard disk contains lots of important information — including books in progress — and the tools I need to get my work done. They understand that without my production computer, there’s very little real work I can do. And even though they don’t necessarily push any harder to complete a job for me than they do for anyone else, they make it seem as if my problem is one of the most important ones they’ll tackle that day. And they soothe me with reasonable reassurances that make it easier to face the 90-mile drive home and wait for their call.

This time around, the problem was a toasted hard disk. Personally, I believe it has something to do with my Firewire ports — it occurred while my iSight was plugged in and I was attempting to suck something off a portable Firewire hard drive. (My motherboard problem also manifested itself when working with multiple Firewire devices, including an iSight, so I’m very wary of using it these days.) They replaced the hard disk — which IS something I could have done myself if I really wanted to — and managed to get about 50% of the data off my old hard disk before it ceased to function at all. This cost me dearly, but the way I see it, I was paying for my own stupidity. If I’d had my entire Home folder backed up, recovery wouldn’t have been necessary at all and I could have saved the $150.

What hurts even more is that I’d written an article for Informit.com about backing up with Fetch before I had the problem and neglected to utilize my own instructions to protect myself.

The computer was done the next day and my husband, Mike, picked it up on his way home. It isn’t exactly on his way — he works about 15 miles north of there — but it was a lot more convenient for him than for me to make the 180-mile round trip drive. On Wednesday morning, I set about restoring the whole computer to it’s normal setup. I didn’t like the way the Apple folks had set up the machine — for some reason I was really bugged about my home folder being called maria (note the lowercase) rather than its usual mlanger (which I’ve used on all my computers for years). (Is that anal or what?) So I pulled off the recovered data, reformatted the hard disk, and spent the next two days installing software and updates. The updates were particularly painful now that I’m on the super-slow wireless Internet connection I whined about elsewhere in this blog. The 139 MB Mac OS X 10.4.8 combined updater took quite a while to suck off the Internet before I could install it.

Fortunately, I managed to pull e-mail messages, endo settings and contents, ecto contents, and some other stuff off my PowerBook. My iCal and Address book data was already set up to synchronize with .Mac, so getting all that data moved over was very easy. The only thing of real value that I lost was Chapter 6 of my Excel 2007 for Windows book, which I’d been working on for the second time. (The first revision went bad and I started from scratch. So today I look forward to starting my Chapter 6 revision for the third time. I knew it would be the book’s Chapter from Hell, but I couldn’t imagine how hellish it would be.)

By Friday, the computer was 90% back to its old self and I was working on it regularly instead of my laptop. So I was out of commission for two full weeks. I blame myself for that, too, letting the disk recovery software run as long as I did before finally bringing it to the geniuses.