0r3jq4a0j
Joined 14 years ago
Joined 14 years ago
They therefore created a default resource structure (probably using the rails scaffold generator command) which includes the id in the URL on all member routes, including the route for the edit action.
Writing, content strategy, curation, copywriting, etc are obviously all important skills. However, being an editor does not remotely qualify someone to run a multimillion dollar business, design software, dictate engineering decisions, etc. Unfortunately, the industry is structured such that they are doing exactly that.
Is it any surprise that slate's division is operating at a loss? It's the norm in a broken industry.
It's completely justified. For example: show me where in Poltz's long career as a writer and editor that he secretly squeezed in the years of UX, design, and development experience that qualifies him to make a statement about designing user interfaces.
The problem is that editors simply don't believe there is special expertise here or that it requires anything beyond their insight.
I admit that I'm not always happy with the result ... http://spectrum.ieee.org/aerospace/astrophysics/the-cosmolog...
This design doesn't incorporate many of the base standards for displaying long-form web content. Font size is way too small (should be 16-18px, 14px absolute minimum), column is too wide ("ideal" is 66 characters, though there's a wide range). A good starter article: http://informationarchitects.net/blog/100e2r/ There are many, many more.
Until that page is completely redesigned and returned to a readable baseline, it's difficult to discuss or test anything.
I can assure you that this is absolutely not the case. If you look at Plotz's comment, it's exactly what most editors will say:
Pages that run too long can irritate readers. We run stories of 2,000, 4,000, even 6,000 words, and to run that much text down a single page can daunt and depress a reader. So pagination can make pages seem more welcoming, more chewable.
They really believe this.
It's important to realize that despite all the buzz about A/B testing in the industry, editors pretty universally believe they don't need to validate their opinions through testing. Why not? Because though school and their careers they've been told that their opinions matter, and, in fact, that's all their job really is: voicing opinions and making judgements, because they believe they have special insight into what readers want.
Look no further than Poltz, a writer and editor with no software design or development experience, who somehow believes he's qualified to make that statement.