Custom Domain with bitly

Okay, I just realized that offers free custom domain shortening. Amazing. I really wonder how they are generating cash out of their service. I would have thought this would be a paid service like custom domains are for

It was quite easy to setup. I first headed over to to grab a free domain (yes, I’m cheap). Unfortunately was already taken so I took All I had to do was set the A record for to and then go over to and add as custom short domain. Finding this setting is a little buried, I had to go to settings and then advanced as opposed to finding it as an option under one of the main tabs like profile.

I’m curious now to see what kind of stats I will get out of my domain shortener now.

Custom Domain for

Well, this evening I decided to fork over the $13 to have a custom domain setup for my blog so you can get here by going to instead of Overall it was a pretty painless process. From the Dashboard I just went to the Store and selectde “Mapping.”


From there I marked that I already own a domain and entered I then paid for it with my PayPal account and was taken to the following screen.


At this point I just hoped over to where I have my domain registered and changed my domain’s name servers to NS1.WORDPRESS.COM and NS2.WORDPRESS.COM. (Full instructions available at 1and1 support)

After this a funny thing happened when I went to Chrome wouldn’t render my site because of a redirect loop. It took a minute for that to make sense. I had my domain at setup to do a HTTP redirect to (the cheap way to do a CNAME Winking smile). Because I had just switched in the above configuration to be the primary domain, was redirecting to where 1and1 redirected me to Ah…the beauty of redirects…

So, I’ll be leaving as the primary until my name server change is propagated through the interwebs.

“Things that are different are not the same”

This sounds like a dumb or obvious thing to say but I can’t count the number of times that this rings true. It’s not a phrase that I came up with, I have to give that credit to a past supervisor of mine. I’d be digging through a page going this has to work. What on earth is wrong with it? It’s the same as this other page. I’d ask my supervisor to take a look as make that very assertion to him and he would respond with “things that are different are not the same.” Man that irked me, but then he would have me go step by step through the problem and proceed to show me where I was doing something different.

I’ve even seen ASP.NET come to this conclusion when it throws an InvalidCastException stating that it cannot cast an object of type foo to type foo. I’m like what the heck! It’s the same type people! Well, what’s happened is that one of the dynamically complied dlls in the ASP.NET temporary files folder got cached and wasn’t deleted properly. So even though the type has the same name, the two types are from a different dll. Thankfully (once you know what is going on) it’s an easy enough fix, just delete the ASP.NET temporary files folder (C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files).

My favorite example of this is in the requirements of a project. “Just copy whatever the page does from over here” or “just make it look the same" they say. Problem number one with this, the BA in this scenario typically doesn’t know what the original page does which leads to the second problem. The second problem appears when you do what they ask and then they realized its not what they wanted or “just change this to be…” comes at you. Let me say that again, “things that are different are not the same.”

I’ve also been bitten by this adage with the infamous copy-paste bug. In this case however, I want the code to do something different but naturally forget to change one string value, enumeration, constant, or what have you. Someday I wish there would be a nationwide ban on copy-paste and other times it’s a life saver.

So in the end, pay attention. Start with the basics. When you are debugging something where everything should work just like this other thing is working or you “only” changed this one thing that doesn’t affect anything else, take a step back. Look at how even the most minute change or difference can cause a problem.