As always, it depends. Arguably,
http://example.com/users/dcurtis/profile is short, but not too short. If a website/service is centered around people, it makes _more_ sense. Else, the longer URLs seem to make more sense.
http://www.amazon.com/wii is only as useful as someone knowing what the Wii is.
I wouldn't consider the users and profile namespaces a mistake. People get cute and it can create a large constraint how your architecture works. Also, URLs structures as such are often a result of some framework behind it. http://example.com/model/controller/view. It expedites development and managing code something fierce. Perhaps there is opportunity for a shortening widget within the MVC pattern. I need to think about it -- or let other smarter people than me think about it. :)
http://www.amazon.com/shamwow is invalid, along with the other permutations I tried. Amazon doesn't have core shortening service, it seems.
I think the issue is more around URLs which can be parsed by a human vs the proverbial querystring. A TinyURL solves technical problems and looks nicer which is 2/3 of the way there. The remainder makes sense to a person.