3 ms·
After four years working in the industry I can say with confidence that in 100% of the news organizations I've interacted with humoring the developers resulted
by knieveltech 16y ago
After four years working in the industry I can say with confidence that in 100% of the news organizations I've interacted with humoring the developers resulted in a disaster. Newspapers are not software shops.
From a business perspective there's no money in humoring the guys in the development department on this one. Money's too scarce. It's cheaper and more effective to can any dissidents, swap in competent PHP developers and go with an implementation that minimizes wheel reinvention and the amount of code the organization is responsible for maintaining.
- natrius 16y agoCheaper? Yes. More effective? Debatable. If a news organization is just trying to put articles online, then sure, that approach works. If they want to push the boundaries of what's possible in online journalism, you're not going to be able to accomplish that by sticking the cheapest cogs in the machine. Armstrong users will only have to maintain their templates and customizations. This is a requirement no matter which CMS you pick.
- knieveltech 16y agoI once cooked up an implementation targeted at the "Local Events" vertical. It implemented 100% of Zvents feature set and took 15 hours to put together. That tells me everything I need to know about effectiveness. Basically my point boils down to this: there are freely available, insanely flexible, totally customizable CMS's that have been under active development for a decade or more. Given how long it takes to create truly polished software of any kind, starting a CMS project from thin air doesn't make sense, you're hundreds of thousands of developer hours behind existing projects on day one.