David Johnson, an Assistant Professor at American University's School of Communication critiques an incredibly weak New York Times article, which "breaks the news" that text-happy teens may suffer health problems as a result of too much of a good thing. Johnson's beef is with the "he said, she said" predictable nature of the storytelling, and I agree with him that it makes for an article that is "Dull, boring, unconstructive, adds no value ..."

I extend on that criticism by suggesting that it is also incredibly lazy journalism. This piece required no original thought, just a couple interviews asking some very obvious questions and citing a couple of "studies." Anything teenagers (and adults for that matter) do too much of is dangerous. This is news? Parents are concerned ... oh my. And any parent who doesn't put a stop to their kids texting them in the middle of the day to ask what shoes to buy has lost the game already anyway.

I have just one question:

What is up with this ridiculous "we need a new CMS" mantra?

We use a home-grown online CMS, that is incredibly efficient at managing the page-container-fragment hierarchy required to build consistently styled and structured web pages. The system doesn't care if the fragment assigned to a given container is a static piece of HTML, some javascript, an ASP.NET user control, whatever. So ultimately it is quite a flexible system.

But inevitably, every time a need arises for a page to look, act or behave differently from our standard set of page templates, the cry goes up for a new CMS. It's too bad the town criers are confusing the CMS with the story and front editing tools sititng on top of it.

How about you guys let those of us who have a deep understanding of how content is stored and retrieved and how web pages are built make the decisions about whether or not a "new CMS" is needed, eh? How about you just try to describe business requirements, and not prescribe technology solutions, eh? How about that? Then maybe we could actually get down to discussing the real issues, and not the red herrings.

For about a month now, we've been working on a publishing system that will embed useful (hopefully) inline links in our stories. This isn't new - other newspaper websites (The New York Times, for example) have been doing this, some for years. But it's new to us and is certain to raise awareness (and maybe hackles) in the newsroom.

My biggest challenge is training the entity extraction system. The term "Jewel" means nothing in the News/Politics section, but has definite meaning in the Life/Music section. Is "Davenport" referring to Iowa, South Carolina or someone's last name? Is it "Michael Jordan" the retired basketball star or "Michael Jordan" the former CEO of EDS? If you're in the Sports section, it should be obvious. Can we expect an automated system to do this? I hope so - I'm working with a company called mSpoke to try to get this accomplished.

The new links will go live on the site some time next week.

There's nothing worse than a project where you end up being the de facto project manager simply and only because nobody else will step up. Even when it's part of their job to do so. The strong temptation is to just say "screw it, let the damn thing flounder" but of course that's not an option. That's not what your work ethic is all about. That's just not what you do.

I keep telling myself to just take pride in the fact that you dragged another one over the finish line, even if you did other people's jobs for them along the way. But those people get plenty of the credit that they don't deserve, over and over again. They don't get fired or laid off. They get promoted. How many times do you have to just take one for the team before it becomes tedious and boring?

There are many types of tech conferences out there, but the ones I find myself most often attending fall into 2 camps: The Microsoft Mix type events, where the vendor hype, buzz and knowledge sharing is heavy and the more private events where development shops get together to discuss trends and best practices and to network, and where vendors are typically not invited.

This week, I'm attending one of the latter in NYC. I'll report back if I learn anything new or pick up any particular insights.