Regardless of what best practice is for developers issuing response codes, designers need to design for the possibility they’ll do it wrong, and provide a good experience to the user nonetheless. As it happens, we do issue 301s, 302s, and 410s, but we design for the possibility that someone may make an error at some point in that process. My goal isn’t to write a technical guide for front-end developers (plenty of those exist already!)
Hi Shaun,
Nat Dudley

Side note: I think it’s interesting that you draw a distinction between Designers and Developers here. Good UX transcends simple boundaries such as design and development. i.e. A developer is just as responsible for UX as a designer. And a designer working on the web medium should care about being good ‘Web Masters’. (Onion layers of UX?)

Like what you read? Give Shaun O'Connell a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.