Tag Archives: Apple

Tumblelogs

Posted on by
Comment

I discover a new, abbreviated form of blogging.

One of the things I’ve noticed about my blog is that a high percentage of the entries are extremely wordy, full of stories or opinions or information that I’ve spent a lot of time thinking about, compiling, formatting, and publishing. And it seems that most serious blogs are the same.

Enter, the tumblelog, which has apparently been around since 2005. This short-form blog is ideal for quick and dirty entry posting. In fact, that’s what it’s supposed to be for.

From Wikipedia:

A tumblelog is a variation of a blog, that favors short-form, mixed-media posts over the longer editorial posts frequently associated with blogging. Common post formats found on tumblelogs include links, photos, quotes, dialogues, and video. Unlike blogs, this format is frequently used to share the author’s creations, discoveries, or experiences without providing a commentary.

I first heard of tumblelogs on either the TWIT or MacBreak Weekly podcast. Leo Laporte and other members of those two podcast teams use Tumblr to create and publish their tumblelogs. Curious, I went to check it out for myself. And, on the FAQs page there, I got a the analogy that sold me on trying it for myself:

If blogs are journals, tumblelogs are scrapbooks.

It might be nice to have an online scrapbook, I thought. I decided to sign up for a free Tumblr account and give it a try. The result is the unimaginatively named Maria’s TumbleLog, which can be found at tumblelog.aneclecticmind.com. (And yes, you can host a tumblelog on Tumblr’s site; I just got fancy and set mine up with my own custom domain name.) Since then, I’ve added entries that include photos and quotes. I’ve also set up my account to automatically create links to new articles in a number of feeds — including the one for this WebLog.

Although I like the ease at which entries can be added to my tumblelog, I don’t like the fact that there’s no offline composition tool. But I think that’s because I’m worried about composition — a task that simply doesn’t apply to tumblelog entries. Entries are extremely short and to the point: a photo with a caption, a quote with the name of the person being quoted, a link all by itself. While it is possible to create a standard text entry, I’m going to try hard not to — unless I can keep it to 100 words or less. That’s not an easy task for me — writing more has always been easier than writing less.

Will anyone read my tumblelog? I don’t know. Do I care? I don’t know that, either.

Right now, the idea is too new to me. I’m more interested in experimenting with this form of expression and seeing whether I can stick to it.

I’ve been blogging for 3-1/2 years now; it’ll be tough to branch some of that energy off to a similar yet very different form.

In the meantime, I’d be very interested in hearing from others with tumblelogs. Use the comments link. And be sure to include a link to your tumblelog in the form so other readers and I can check it out.

Web Site vs. Blog

Posted on by
10

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.

On Geniuses

Posted on by
6

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.

Backup at the Touch of a Button?

Posted on by
5

We’ll see.

The first thing I did when my hard disk failed on Friday (for the fourth time in less than 10 years) was to go online and find an external hard disk that had enough capacity to back up my computer’s entire hard disk. And while I was at it, I’d get one that was bigger than my current hard disk so I could use it for my next computer (which will probably be purchased sometime before the end of this year).

Seagate ST3300601CB-RK 300 GB External Hard Drive with FireWire and USB 2.0 InterfaceI started at the Apple store, figuring that the products sold there would work effortlessly with my Mac. I found a Seagate 300 GB model (the Seagate ST3300601CB-RK) that boasted “pushbutton backup.” Now that sounded like the right thing for me. I did a little Web searching and found the same hard disk on Amazon.com for $40 less. I ordered it. It should arrive sometime next week — hopefully right around the same time TechTool Pro finishes doing whatever it can to recover my data.

SmartDisk FWFL80 80GB Firelite 2.5In the meantime, I still have two 80GB Smart Disk FireLite portable Firewire hard disks to capture whatever can be scavenged from the disk.

I’d like to hear from readers about backup strategies and solutions, as well as any experiences with Seagate’s “award-winning Bounceback Express software.” (I’m extemely skeptical about this solution.) Use the Comments link. And if you want to share a hard disk crash story with us, please do. I can’t be the only one out there losing hard disks.

A Helicopter Repair Story

Posted on by
Comment

Including a happy ending.

On Tuesday, I flew out to Robson’s Mining World in Aguila, AZ. I was scheduled to appear there on Saturday for their anniversary celebration and I wanted to make sure my usual landing zone was in good shape.

It was a windy day and I was tossed around a bit on the 8-minute flight from Wickenburg (vs. a 30-minute drive). But the winds were calmer closer to the ground. I circled Robson’s once, then set down on what I thought was a spot closer to the road. Turned out, it was the same spot I’d occupied the year before. It just looked closer to the road from the air. The quartz rocks Mike and John had laid out in a line for me were still there. The idea was to land with the helicopter’s cockpit over the line. That would keep my tail rotor away from the bushes behind us. But since the bushes looked bigger than they had the year before, I positioned the helicopter a little bit closer to the road.

I cooled down the helicopter and shut down the engine. Then I went out to assess the landing zone on foot. I discovered that the quartz line was still quite workable for me. The bushes were farther back than I’d thought on landing. (I always estimate the helicopter’s tail longer than it really is.) So the landing zone was fine. No trimming would be required. That’s good because I don’t like the idea of cutting any desert vegetation unless absolutely necessary.

I put on my jacket — it was still quite cool at 9 AM — and walked through Robson’s front gates. The place looked deserted. I headed toward the restaurant, planning on having a piece of pie for breakfast. The door was locked but as I was starting to turn away, Rosa, who works in the restaurant, hurried out from the kitchen and opened the door. I settled down at a table and she talked me into having a real breakfast of bacon and eggs. She set me up with a small pot of hot tea and went back into the kitchen to prepare my food.

I had a few awkward moments when the teapot’s lid fell into my cup and became stuck there. If I’d been with someone, we would have been laughing hard. But I was alone and laughed at myself more quietly. I had to pour all the tea back into the pot and wait for the lid in the cup to cool and contract a tiny bit before I could get it out.

Rosa brought me a plate of fresh fruit — grapefruit, pineapple, grapes, and oranges — then disappeared back into the kitchen. I busied myself by reading the history of Robson’s and some information about the equipment and vehicles on display. When she brought out my breakfast a while later, I gobbled down the two eggs over medium, three slices of bacon, and two slices of wheat toast with real butter. (Don’t you hate when restaurants use mystery spread on toast?)

The person I was hoping to see there, Rebecca, wasn’t in yet. She lives in Wickenburg and drives out five days a week to manage the place. I saw her drive in just as I was starting the engine for the helicopter at about 9:45. Since the engine was already running and the blades were already turning, I didn’t shut down. I had another stop to make.
Continue reading →