Tag Archives: code

Is your newspaper.com is a big ball of mud?

Is your newspaper site a clean-looking, uniform grid of semantic (and validated!) code? Or is it a ‘big ball of mud,’ with includes (scotch tape) and javascript (bubble gum) holding together a jumble of disparate hunks of content?

If you answered ‘YES’ to the first question, congratulations, you work at the New York Times, or the Guardian, or maybe a paper running on Ellington. (Yes, yes, feel free to point out your own brilliantly integrated newspaper.com in the comments. Humor me for a moment, mkay?)

But for most of us, that second answer is a reality as newspapers try to race to build and improve functionality that’s built in to more agile systems across the web.

Comments? Yeah, we’ve got a script for that around here somewhere.

Related stories? Uh, sure, I’ll just write something that queries the database for stuff from the same section with a search for a couple keywords built into it, host it on the only server we have around that runs PHP, then write a piece of javascript to call it in each article page.

And now, the buried lede:

Scott Rosenberg (let’s call him a co-founder of Salon.com to get your attention) has a fascinating post up describing a somewhat academic paper about programming that analyzes the “Big Ball of Mud” style of coding and finds some advantages to it:

Foote and Yoder draw a real-world comparison to shantytowns; they’re ubiquitous because they use abundant materials and require only the most basic skills. Similarly, the Big Ball of Mud “doesn’t require a hyperproductive virtuoso architect at every keyboard.” There may even be a “secret advantage” in its “casual, undifferentiated structure”: “forces acting between two parts of the system can be directly addressed without having to worry about undermining the system’s grander architectural aspirations.”

What do you think?

As a user of a news CMS, you might not notice all the scotch tape and bubble gum, but I’d love to hear from developers and designers about whether you think it’s better to aspire to a clean all-encompassing publishing solution or to just keep dancing dirty and refining the connections between your resources as needs arise.