I've heard this said about difficult passwords, but I think this is putting too fine a point on it. Passwords don't encourage anything on their own, except perhaps a consciousness of the basics of security. It's akin to saying that pizza encourages eating it for every meal. I don't think we've yet seen a gene that selfish.
I am also fine with passwords, but I really dislike useless parallels:
Passwords have to be remembered and therefore having many different passwords cause inconvenience. How does this apply to pizza?
Of course, I only use one computer rather than five different laptops, three tablets and fifty-two smartphones, in which case I imagine it to be tedious to sync them (unless you trust Opera enough to use Opera Sync or some such thing).
Since I need Linux support I use KeePass 1.x [1] on Windows and KeePassX [2] on Linux and Mac OS X. Both versions are free software. They store password entries in a single AES-encrypted container, use in-RAM encryption and allow you to attach a file with arbitrary binary data to each password entry (handy for key files). While there is no single Firefox extension that works across all the platforms they both can emulate typing for password entry. For synchronization I keep the encrypted password file in my Dropbox. If your use case is similar to mine I can highly recommend this solution because it behaves consistently across the platforms I've tried it on [3]. There's also KeePassDroid for Android that supposedly works well with Dropbox but I haven't used it.
[3] The most exotic one being Debian PPC. Sadly, it didn't last since while KeePassX worked fine on it there was no straightforward way to get Dropbox running on non-x86 Linux and using a workaround like rsyncing with an x86 Linux machine running Dropbox or a VM introduced a large extra breaking point to the system.
I've never understood the argument against complex, unique passwords when there are numerous robust, free, and cross platform tools for pw management. It's far easier to manage one database of generated credentials than to remember even a handful of sets of simple auths.
Sync that with your KeePassX and Dropbox and you might just be good to go.
Using a service like twitter as online identity helps to some degree with having fewer passwords except that then cracking a twitter account gives you access to everything.
If you have the $79/year Amazon Prime subscription, then they _do_ default to the "free" 2-day shipping on eligible orders. I don't think they're trying to optimize the flow for occasional shoppers.
Some evil UX patterns are:
* Opt-in: Prepopulating option with more expensive or recurring payment. (example was a donation, but Amazon does this when not defaulting to free 5-7 day ground shipping after promising free shipping prior to putting it in cart! which is much worse since they are bait and switching)
* Opt-in, part 2: Making changes subtle changes can be evil. By switching around buttons, etc. after having it work a certain way a long time and not changing the interface enough, you trigger muscle memory to do the wrong thing. Amazon has exploited this as well with the (not) free shipping option.
* Difficult to quit/cancel: also mentioned in the OP's linked presentation. In addition to more steps or having to email, etc. they don't even give you a documented option, e.g. you have to email them so they will delete your account and they say that nowhere in the site.
* Glossing over legal: Small text or less readable font to hide details is evil.
* Hiding legal: putting legal disclaimers in an area of the site that is hard to get to is evil.
* Unnecessary login: making the user login because they might want to retain info about something, when really the site owner is getting more benefit (selling email address or lead info, mining it themselves, etc.).
* Asking for more than is needed for user to accomplish what they want: asking the user for more info than they need to provide in order to get lead info when they are not aware you will contact them is evil.
* Unintended use of data: Worked for a telecom that had page to get phone# to look up service availability and then they would use that for lead info.
* Easy to determine security questions: this is just stupid. Many are easy to find out and they do little more than make the uninformed user feel more secure. Examples: birthday, street you grew up on, etc. that can be learned even without social engineering.
* Passwords: one of the most archaic and stupid constructs ever. Passwords encourage people to use the same password across sites, so if one is compromised, they all are. An autogenerated passkey and a more secure way to reset it with a new one if your passkey was lost or stolen would beat passwords anyday. SSO only compounds this idiotic UX we can't get rid of. (And we put abusable/hackable cameras in every laptop instead of adding retinal scanners or thumbprint readers in every laptop, which could be viable alternatives.)