Goran Peuc has written a pretty interesting post on what web developers should stop doing now that we’ve hit 2014. While the bullet point format is interesting albeit a bit tired (“5 things you shouldn’t do on your website”), it gives a good set of pointers for the people most removed from being a non-technical user. However, the really interesting part of the post is Peuc’s point about the relationship between a horrible user experience and developers in discussing PayPal’s ridiculous credit card input field:

Yes, you got that right, developers of the site force the user to understand how the backend logic of the website works.

If we extrapolate this a little, it reveals one of the main causes of bad user experiences: developers forcing users to do the developers’ job, as my colleague Casper Lemming so gracefully puts it. I know that communication is not always the average developer’s strongest suit, and of course, all abstractions are generally leaky, but it’s 2014. The .com days of “you know HTML? You’re hired!” are over — if you’re building front facing stuff, as most web developers are these days, your job is as much a communications job as it is a developer job.

Really, then, screw the bullet points — your developers should stop making users do their job.