|
|
|
|
|
by albertsun
3887 days ago
|
|
It's really depressing how cynical that is. (Developer working at the NYTimes here). The actual reason links to studies are often left off articles (particularly in cases like this with sharp deadline pressure to publish fast before the competition) is that the software powering the editing and publishing workflow really badly needs improvement. An incredible amount of work and knowledge goes into a story like this. Versioning rich text through many different software tools designed for writing/editing and publishing across many platforms is hard. Sometimes people copy/paste by hand and in doing so a link can go missing. The news industry needs more technologists to work on these problems. We're hiring for people to do that, by the way: http://developers.nytimes.com/careers/ (Also, the link to the study is now in.) |
|
Now I don't want it to sound dismissive or personal in any way, but tell me - if say, few of great software devs now drop everything they do and come to NYT to help, sit down for months and develop the most awesome software package the world of press has ever seen, will it actually solve the quality issues articles have? And more importantly, if sold to other papers, will it suddenly solve their problems?
Will it make journalism honest and trustworthy instead of lies and clickbait bullshit?
I'm not sure how much blame to put on broken publishing workflow, a lot of this seems really to be about broken incentives - "deadline pressure to publish fast before the competition" that leads to the "many articles, as sensationalist as possible, truth be damned" mentality, especially in the management layer.
But you did give me a pause here. Only recently I had a chance to peek at internals of a tiny part of manufacturing industry, and oh boy how much money they waste on badly designed software, which is badly designed because of deadline pressure and top management pressuring to iterate over a broken software package (and then messing with the process) instead of scrapping it altogether and doing it right. Maybe software is more to blame than I thought.