Skip to main content

Bonehead of the Week: PB Furniture

My wife kicked into an organizing spree last week purchasing a companion shelving unit to house kid stuff matching one we already have. I took an hour or so putting this second unit together Saturday. I'm one screw away from finishing and...crap, this one isn't the same color. You've got to be kidding. Explicative. Explicative. Explicative.

Yep, the new one is "espresso" with the old being "honey". C'mon, get real people. I'm completely pissed at myself for not checking and/or noticing sooner. Taking this guy apart isn't tough but putting it back into the need-to-be-a-packaging-engineer packaging feels daunting. Well, I managed to get it close and re-pack it with some semblance...and off to Easton I go.

My wife called ahead and Pottery Barn Kids told us to just have our receipt and pull into a little, nearby driveway. Ok, fine. Well, they've changed the traffic patterns at Easton and it's a PITA to get around; but I finally plunk myself in the right spot.

I hop out of the T-Blazer and blam, Mr. PBK is wheeling my replacement shelves out. Is this guy psychic? We exchange boxes and he inquires, "You just called a few minutes ago, right?" [Nope...but I'm hijacking these "honey" shelves nonetheless, pal.] About then, a mini-van pulls up. Yep, you guessed it: two people pulled into this loading dock, both at Easton, both at exactly the same time--both retrieving the exact same thing. Doooo-dooo-dooo-dooo. Creepy, right?

Needless to say, I checked for the "honey" color prior to departing. Yep. "honey". Grumble. Grumble. Metrosexual. Grumble. Well now I'm an expert. I set up my "honey" shelves in about 25 minutes.

All is well (and organized) now! Unfortunately, due to my push to get this task checked off my list, a 45 minute task became a 4 hour task. Super.

Comments

Popular posts from this blog

Hero Write-up: Now this is Customer Service!

My best friend Scott is president/C-everything of a small northeastern Ohio manufacturing concern, KirkKey Interlock . I hadn't spoken with him for a while and wanted to see how Canton fared with the Blizzard of '08 (that's what they're calling it...not me). I say, "So what's new?" He replies that on Tuesday his primary server (which essentially runs the business) came up with lame with not one, but [a statistically improbable] *two* physical disk failures on a RAID5 hardware array. My friend attempts the fix but gives up pretty quickly after seeing some Linux nasty-grams on the boot screen. His service provider is an old college buddy who lives down in Raleigh, Cerient Technologies led by Jason Tower . Scott couldn't email out because Exchange was on the toasted server. Being creative, Scott started Treo-emailing photos of the screen. Unfortunately, Jason couldn't receive email because a storm had knocked out a lot of local hosting. [Sigh] After...

Certified or Certifiable?

As a senior technology professional, I interview a lot of candidates. I also maintain solid relationships with other folks in the community. Frequently, the topic of certifications arises: A good investment? Valuable? A clear measurement of skill? Consensus appears to draw the line related to one's seniority. If you're (for example) just out of school and looking for an instant creditability boost, by all means pursue a certification. Likely, this credential will assist you in overcoming the "junior" tag and likely land you more interviews and client roles. (Note: I'm going to use the terms senior and junior here...no offense to either. Can't think of a better one word description. I was a junior once too.) In stark contrast, the value of certifications drops off the table around the 2-3 year mark. Some in my circles even perceive certifications as a negative for the senior professional. They think, "If this guy is so solid, why is he wasting valuable...

Lab Management in Visual Studio 2010 Released

In my experience, there's a lot of animosity and poor communication between Development and QA . It's not that they don't appreciate one another so much as they never seem to stay on the same page. QA : "What's the status on defect #4874?" Dev: "Done." QA : "Done?" Dev: "Yeah, I fixed that Tuesday." QA : "Err, ok . Well where is it? I mean where can I verify it?" Dev: "No clue. I committed it Tuesday. It passed unit tests and built successfully." QA : "Alright. I'll track it down." Invariably , QA speaks with the build manager (if there is one) to find the build in which that defect was repaired. After discovering the correct build, now QA needs an environment stood up to house that build. But wait, the UAT environment is currently testing the next release. It can't be disturbed for another week. At this point, the QA person's blood pressure heads for unsafe levels and the Dice.com bro...