Skip to main content

Time Travel

 On November 25th, I ordered a couple of items from Bed, Bath & Beyond. It was late on Thanksgiving, I was up and decided to take a quick look at early Black Friday deals. The air fryer I had been eyeing for a few months was finally on sale. And I needed a comforter set. So why not kill 2 birds with one stone? I ordered both items for delivery (2-3 business days). Whatever, not an urgent need. 

Friday afternoon, I received an email from BBB, my items have been split into 2 shipments. The first shipment is on the way. Here's the tracking number. Oh nice...I clicked on the tracking number and got this:

I do not list in NJ

Go ahead, click on it and take a look at the dates. According to that tracking info, the package was shipped on October 13th! Yeah, that's the reason for the title of this post. Somehow, BBB issued an already-used tracking number for my shipment. It gets worse. Both shipments were assigned different used tracking numbers. Both tracking numbers were for packages shipped before I even placed my order. So either BBB and/or their shipping partner royally screwed up or we've got a time-travelling package. 

I called BBB, spent over 3 hours across multiples calls over multiple days with them. Bottom line, they couldn't explain it either. They decided to ship me replacements. Fine...can you expedite it? Sorry, we can't do that. It'll take 7-10 business days! At this point, I was royally pissed. So they issued a replacement order and gave me the new order number. Couple of days later, I go to check the status of that order and guess what? Their website can't find the new/replacement order number. Great...just great. Decided to call back. This time their automated phone system had the new tracking info...just wait for it to arrive. Somehow, at the back of my mind I kept wondering how the heck does this happen? USPS or whoever they use can't just time-travel a shipment to the past. I wondered if both shipments will end up arriving...yep, that's exactly what happened. 

First, the air fryer...oh nice. Started using it; not super impressed but that's a story for another day. Couple of days later, a package shows up at the door. Great, I thought, the comforter set has arrived. But no, it's another air fryer. I put it in the garage...I'll deal with this later. Next day, the comforter set arrived. Day after that, a second comforter set arrives. 

Obviously, I can't keep them. So now I've got to call them to come pick up their stuff or I've gotta schlep them over to the Bed, Bath & Beyond store. 


Popular posts from this blog

InfoPath & SharePoint (Part 1)

A departure from sports and politics. This one is about technology. InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment , has absolutely no redeeming value. It's worthless and if your boss ever thinks of using it, you have three options: convince him not to (not easy once he's been brainwashed by the Microsoft marketing presentations) use one of Al Gore 's lockboxes to store away your sanity 'cos you'll lose it. Also, pad your estimates very generously . You'll need every bit of time you can get. quit immediately while you still have your sanity First, InfoPath: To me InfoPath is like programming in assembly language . Sure it makes it easy (too easy in fact) to bind data to controls. But it doesn't provide you with easy access to your controls. Why is this important? Say you want to disable a button : in most technology: buttonA.enabled = false (or something similar). In InfoPath, you simply

Does InfoPath (still) suck?

A couple of years ago, I wrote a blog post titled "InfoPath & SharePoint (Part 1)". Back then I had just started working on a project using InfoPath 2007. So, expectedly, the post wasn't very complimentary to InfoPath (or SharePoint). In fact, I said: InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless.... ( more ) Since then my opinion of InfoPath has changed slightly. It still suffers from all the flaws I pointed out in that post. However, I think when used right, InfoPath can be an OK tool. I think it's well suited for designing one off forms and not for anything that requires complex logic or multiple iterations (like most software development requires). Alas, most CTOs fall in love with its point & click simplicity and integration with SharePoint that they try to use it to replace more developed technologies like ASP.NET. What do you get? A h

Technical Certifications are worthless

Technical certifications, especially in the IT field, are totally worthless. Why? All a technical certification prove is that you were able to buy a couple of exam prep books, cram them in a week or two and take an exam. My monkey (if I had one) could do that. I can't tell you how many times I have interviewed certification-carrying candidates for open positions at my company only to find them severely lacking in thorough understanding of computer science. I don't care that you have an MSCD or MCP or whatever it's called these days if you don't know foundational concepts in computer science and database design. For example, I don't want someone who just knows that you store things in a hashtable using keys. I need you to know why a hashtable is better than an array in some cases. I need you to know when an interface is better than an abstract class; when to use recursion; the different kinds of joins and when to use each one; I need you to understand how crucial so