Skip to main content

What can brown do for you?

Apparently, it can drive you insane, especially if you haven't dealt with it before. They use a number of very simple, but effective methods:
  1. They only deliver, when you are not there, e.g. between 9 AM and 5 PM, and leave a note you can't read with a reference number.
  2. Since you weren't there, they will deliver again the very next day, making sure they attempt the delivery at the exact same time (because they already know, you wouldn't be there). They will leave a note with a different reference number.
  3. They will  try again (same time) next day, and then leave another note with another reference number, marked "final attempt".
  4. You will call the number on the note to figure out what's going on. Eventually you will get a live person, who will be very helpful and reschedule the delivery for the time you can be there (after 6 PM).
  5. They will deliver again next day around noon, and leave a note with a new reference number.
  6. You will call. After getting a live person and explaining the situation, you will be told "I am really sorry, but whoever promised you any delivery after 6 PM, shouldn't have done that, because we only deliver from 9 AM to 5 PM. Alternatively, you can pick up the package at this location (address follows). It's open from 9 AM to 5 PM Monday through Friday. Oh, you can't... What we can do is try to deliver to your work address, if it's convenient for you?" You will give them you work address, directions, and name of the receptionist on the first floor.
  7. They will deliver again the next day, still at your home address, around noon, and leave new note with a new reference number. You will call to find out that they are sorry, but it usually takes more than one day to change the delivery address, but it should be redelivered tomorrow.
  8. They will deliver again at the new address. The other two packages you had, were still delivered to your original address, but due to pure coincidence, someone was at home at the time of their arrival, and was able to receive them.

... so I instructed my daughter to change the delivery address on file for her gift registry to my work address. I wonder what is to happen now.

Labels:

Popular posts from this blog

Who is running MacAddict forums?

I normally hate to complain, but, being a happy subscriber to the magazine for some time now, feel like I do need to express a concern about my recent experience with MacAddict forums section of the web site. Due to some server misbehavior, I had to re-register, my old profile disappeared, while I was updating it. My new profile was assign a label "n00b" (None Of Our Business, if I am not mistaken. This is some way to welcome a new member to the MacAddict community). It could've been cute, but it isn't. And I don't think, it was intended to be: from the post of "Scott": "...using tables for layout...is for lame-ass n00bs..." I have read several more posts in the "Web Design and Development" forum, which, for some reason, was for a couple of days named "George" (the name is back to normal now; but here is how forum moderator "Gipetto" reacted when he was asked about this oddity: "...poop, it blew me away tha...
Read more

{position:fixed} in iOS 6

I stumbled upon this oddity when upgrading to iOS 6 while working on a mobile advertising project, and it took me a better part of the day to figure out what is going on: all of a sudden an element {position:fixed} stopped working in a correct manner (which is staying put, while the page is scrolling), and started "sticking" to the scrolling page, moving out of the viewport, and then just "jumping" back to the correct location after the scrolling was finished.If you scroll this page , you will see it—hint: that's the one labeled "broken"—assuming that you have a correct device/browser combination. Mine was iPhone4 and iOS 6.0 (6.0.1-6.1.3 behaves just the same). On the original page, where I first encountered the problem, all of my elements were created dynamically using JavaScript, but at the end of the day (literally) it become clear, that the glitch is in the iOS 6 CSS implementation.Here is what happens: if you have an element {position:fixed} whic...
Read more

May 1st Reboot 2016

My main site gets a facelift (about half-a-decade overdue). Due to a chronic caching issues with iPage, I have to model everything on CodePen , and then FTP files to iPage, where, for some mysterious reason, html gets updated instantly, but CSS and Javascripts marinate somewhere for at least half an hour, before starting to render, which makes it impossible to model anything in real time. Annoying. Oh, well. At least I finally got to re-doing the site. I still do not have a concept for the galleries, though, and a main navigation menu is really primitive, but the new site is HTML5, CSS3 and what not, and I am not ashamed to refer people to it anymore. Yay. P.S. Resolved the cache issue with .htaccess file: FileETag None Header unset ETag Header set Cache-Control "max-age=0, no-cache, no-store, must-revalidate" Header set Pragma "no-cache" Header set Expires "Wed, 11 Jan 1984 05:00:00 GMT"  everything now works a lot livelier. P.P.S. Why is Blo...
Read more