[TeMPOraL]

The third example (locksmiths) I get, they're making a little show to avoid a difficult conversation with some customers[0]. A bit scummy, but then again, plenty of customers are no saints themselves. However, the first two examples feel like self-fulfilling prophesies to me.

Normal people have no reference point to judge how fast or slow software and hardware should be, other than through direct experience. By adding fake delays to avoid being honest and perhaps reassuring occasional surprised users, vendors just screw with the mental frameworks people build, at scale. It's a wasted opportunity, too, because if you're brave enough to be honest about execution time and weather the initial wave of distrust, then you may become a new reference point for your users, who will now view your competitors' software as bloated.

--

[0] - Though recently I brought this story up with a locksmith, and he said he thinks it's just stupid and there are hardly any situations in which it would even make sense.

[bombcar]

I think the locksmith thing comes from a couple of things:

1. Some disreputable locksmiths (word gets around) - probably very few

2. A locksmith will try the fast methods first, if they work he wins, if they don’t he didn’t waste too much time.

3. After doing a lock once he could immediately redo the same lock much faster and this may make it look like he could have done it very fast to begin