michaelt.smith.net

 

Archive for the ‘Weblog’ Category

Apple let me down.

So, Apple did it.

They have finally let me down.

Apple has, in my eyes, always had a golden hue. Ever since fifth grade playing Oregon Trail and seeing the first PowerMac (with this funny thing called electronic mail) Apple has always been my brand. The brand that I argue for. Need something? Apple can do it.

When Apple built the SoHo Apple store, then the Fifth Avenue Apple Cube and now the 14th Street Apple store, I realized that the company whom I have loved was moving into a new direction and I was excited. Rightfully so. Even after buying a lemon iBook and having it replaced with a brand new MacBook last summer. Even after having my 8 month old iPod fail and being handed an upgraded, brand new iPod.

Last week, in the course of my daily work, I needed, urgently, a LaCie Rugged 250gb hard drive. I called the SoHo Apple store and was told that that they had it in stock… but I should hurry down as they only had a few left. Okay, now chances are that there isn’t a constant run on Apple stores, but still, I asked: “Well, how many is a few.” But, do to “confidentiality” they couldn’t actually tell me. Odd. So, I hung up, a bit more confused than anything else.

Fast forward an hour, and I have now decided to downgrade to the LaCie Rugged 120gb hard drive for the lab. Called the Apple Store again to check. This time I was told that they sold them but due to confidentiality, they couldn’t tell me if they actually had any in stock. Now that just seemed a bit crazy. So I pushed a bit further — eventually I was told by the customer service person that even if they were allowed to tell me, she couldn’t because she is very busy, the people in the store are very busy, and that no one would be able to check and get back to me.

The story ends with me buying the hard drive from the NYU computer store, getting a $10 discount for the lab and being happy. So…, it worked out, right? No. The Apple store had made it clear to me that they wouldn’t assist me. Now granted, they may have been too busy to check exactly how many their were or to hold one for me, but to tell me that due to confidentiality they couldn’t tell me? Seems like an odd reason to say ‘no.’

I’ve had amazing customer service experiences with Apple in the past, so you best believe that this hasn’t made me a cynic or a hater. But it, at least for me, shows that no matter how well designed, how well functioning or how well liked your product is, if the “interface” doesn’t work, you’re probably going to get burned. In this case, Apple’s interface for this transaction—the staff member on the phone—tarnished the great product being sold by Apple and I ultimately went to a competitor. For me, this “issue” isn’t one related only to customer service but to any area where there is an intermediary between you and your customer.

AJAX-Happy

With the advent of easy to use frameworks like MooTools, Prototype and, my favorite, jQuery over-zealous use of javascript to create pretty user interfaces is everywhere. As a young developer, one of my most important lessons, that I’m attempting to try to learn with every new project, is where and when to implement this “web 2.0″, “AJAX” goodness, and when to just to go back to the tried and true html+coding language of your choice standard.
Case in point:

Inability

Sitting in the doctor’s office the other morning, I realized I had an inability to do anything. Now, mind you, I think myself a capable person, but I had been put (or put myself, rather) in a position where I couldn’t do anything. Sure, I had my copy of the Times with me, which I had read for the past hour (train ride, plus some waiting room time), but ultimately I couldn’t do any work. The doctor was running late, I was sitting; twiddling.

I took an inventory: I had two client sites I could make some progress on, I had my portfolio I could keep developing, a bunch of articles to read (I’m a bit behind on A List Apart & 24Ways), a few e-mails to send, and then, of course, there was actual day job “work” that I could’ve done (some journal articles to read.)

I did have a few PDFs of some articles to read, and after skimming them, I was ready to work. But I couldn’t work: The client sites, while on development areas of the servers, were exactly that–on a server. No problem, I had Transmit and TextMate. An sFTP connection, a SSH tunnel for mySQL and I’d be fine. Nope. Problem. My doctor’s office had locked up their wireless network (which I guess I should be thankful for.) Suprisingly, though, no other wireless network in the building was available (again smart, but painful.)

One of my leading problems is that I have a MacBook and a Mac Mini at home that I use regularly. I don’t use one more than the other for working on any one task; the actual environment decides the computer. I will commonly sit on my bed, at the kitchen table or on the couch and work on the laptop. If I am trying to focus I may work on the mini on my desk. If I am traveling, then the MacBook becomes a one man show.

The problem is that I now have multiple avenues to conquer singular tasks.

What my first writings in this log are going to be about conquering the environmental constraints of working with multiple computers. My next post will be about the challenges I face while setting up developmental servers.