5 ms·
> 1. Lack of a real technical / engineering department. Having said that, their core business is news and they really just need a functioning website, not a ful
by ryandrake 8y ago
> 1. Lack of a real technical / engineering department. Having said that, their core business is news and they really just need a functioning website, not a full (and expensive) engineering department.
I agree with the rest of your points but this one doesn't really make sense. My guess is it would take fewer engineers to make these websites better. The horrible parts of newspaper websites are the pop-ups and broken scrolling and ads that follow you and fixed-position "dickbars" at the top and bottom--things that don't come with simple HTML and need to be deliberately added by developers.
Newspapers really do just need a functioning website. Instead they pay developers to add in all these horrible things.
- jasoncartwright 8y agoSlight aside: Django came out of a local newspaper https://en.wikipedia.org/wiki/Django_(web_framework)#History https://en.wikipedia.org/wiki/Django_(web_framework)#History
- knowtheory 8y agoRight, and it's still sad to say that they capitalized on that fact so incredibly poorly that the following came to pass: https://twitter.com/jacobian/status/1012781017940316161 https://twitter.com/jacobian/status/1012781017940316161 > The Lawrence Journal-World, where Django was created, is now a Wordpress site. http://www2.ljworld.com/news/2018/jun/26/redesign-ljworld/ http://www2.ljworld.com/news/2018/jun/26/redesign-ljworld/
- always_good 8y agoOr they realized that there isn't much value in building their own CMS.
- ubernostrum 8y agoI worked at the Journal-World for around five years, starting in 2006. Upper management at the time was interesting. A lot of people who didn't necessarily understand the internet or technology in general, but knew they didn't, and were willing to hire and trust people who did. That was the magic sauce that led to Django, and a lot of the other innovative stuff. The owner of the paper, for example, had his secretary print out his emails and bring them into his office; then he'd write his replies on a manual typewriter, and hand them back to be typed into a computer. But he'd also managed to ride the wave of first the cable TV/internet boom (by setting up a cable division) and then the web boom (by hiring a team of people to build a first-class news site and giving them more or less free reign to do it right). And that was how you got the heyday of the Journal-World. All sorts of interesting experiments in using the web to enhance journalism, close collaboration between the newsroom and the tech team, and a ton of cool things accomplished and a bunch of industry awards, etc. I actually had a byline at one point, on a feature that's now gone because Django got retired (a data-journalism project tracking the impact of flu during the H1N1 scare). And other news organizations were happy to pay for the software to do their own version of that. We had both hosted and on-prem versions of it, and recommendations for hiring developers and training them to work on it, and as far as I could tell they seemed pretty happy to have something that had been designed at and by a newspaper (as opposed to other news CMS products, which often have their first encounter with a journalist at the time of production deployment). But all good things come to an end. There were some management shakeups, and a lot of the tech team (myself included) left for greener pastures. A little while after that, I heard the CMS division was being shut down and everyone in it laid off; then I heard another company had made an offer to acquire it. As far as I know, Ellington (the Django-based news CMS) is still available today as a supported commercial product. But the Journal-World no longer uses it or, to my knowledge, maintains an in-house technology team like it used to.
- snowwrestler 8y agoIt makes total sense to me. Having web developers is not the same thing as "a real technical / engineering department." Most of the cruft on newspapers sites is not carefully implemented custom code. It's a library, or vendor-supplied code, or CMS plugin that is just installed, configured, and forgotten about. Without strong engineering leadership, shit just gets piled on top of shit as the feature requests come in. Which also relates to items 3 and 4... without strong technical leadership, a developer team can easily just settle into triage/service mode, where they just try to keep up with satisfying each request that comes in. The result is growing technical debt and an unfocused, confused product.
- ryandrake 8y agoSure, it would take better engineers to build better cruft. It would take fewer engineers to not build it in the first place.
- dsfyu404ed 8y ago> Having web developers is not the same thing as "a real technical / engineering department." That's a dangerous opinion to have around these parts. ;)
- TangoTrotFox 8y agoI think, like the article hits on, this comes down to the fact that users have a rather different definition of "functioning website" than advertising driven news sites do.
- WalterSear 8y agoNot fewer - better.
- rokhayakebe 8y agoI have never seen a non-tech business (law firm, dental practice, newspaper org, etc...) that could not use one or two engineers and give their business major advantage against their competitors. Unfortunately, you cannot convince them of this.