“There’s missing support for the middle-class of news developers. This is a particularly glaring gap, because it’s the most difficult part of the incubation of the adolescent coder.”

That’s Jeremy Bowers, as quoted here and here. And I totally buy it. As someone who’s learned enough PHP/WordPress to understand and poke around at what could be, I’m utterly lost on how to go from tinkerer to real-deal maker. Especially in other languages.

We bundle information over time: instead of reporting everything as we find it out live, we gather up all kinds of related information and bundle it into a story. Bundles come in different sizes: we can churn out a quick news report in half an hour, or we can save up months of work for an enterprise story. They also come in different colors: most often we bundle topically related information (a story), but sometimes we bundle by type of information (a rumors section) or time (today’s linkblog).

We also bundle — weave — information into narratives. Stories are not concatenated facts, they’re not bullet-point lists. Stories combine related information and glue it together in paragraphs. Let’s call these narratives blobs.

The middle ground, I comment, has to be providing improving the way we contextualize those bundles of facts that are getting smaller and smaller as our news cycles quicken:

Well said, as usual, Stijn.

The fact that unbundling has become sort of a default setting for fast-paced news organizations these days is all the more reason that we should be focusing on a better contextualization. Important news tends to come in storylines — but besides simple tagging (lame), we don’t really organize these episodic events into order. And we certainly don’t indicate to readers which episodes were more important than others. Coupling our quick-hit stories with big-picture analysis on regular basis would be a huge public service.

Really, I just wanted to write. I had done far, far more editing in the last 18 months at The Hatchet than original writing, and my new gig with POLITICO was going swimmingly, but didn’t allow for a writing anything longer than a caption. So, I made a Tumblr. As you can see by the first post, it was supposed to be the happy medium between my 140-character tweets and longer, professionally-themed posts here on WordPress. I had a few nice entries, with a marginally-witty post here and a good reflection there.

Then,they became a little less frequent. Then, a little less. Then, nothing.

I’m a little disappointed that I stopped writing and let never really let my Tumblr get off the ground. But I didn’t stop writing because I decided to sit around and be lazy with my free time instead of using my creative outlet. No, I found a new skill to work on.

Coding.

I’m not programming yet (though I’m trying to learn if you want to help teach me,) but over the last few months I’ve really taken an Olympic leap into Web design and site-building. Sometime next month I will close the book on my seventh site of 2010 (note to self: update your portfolio.) At the beginning of this year, saying that I’d build seven websites from scratch in the next 12 months would have been high comedy. I’m proud of what I’ve done (and eager to learn more and get better every day) but there have been a couple moments where I’ve wondered if I my time could be better spent.

See, I’m a journalist. A writer, you know. Someone who crafts messages with the written word. I don’t do design. I don’t do code. I didn’t major in computer science. I like technology, but I’m not a web geek, right? Right? RIGHT?!?!

At this point, who knows? I’ve always thought of myself as first and foremost a writer, but I spent most of my day off yesterday learning about how to build and utilize custom post types and child themes instead of reading the latest top stories and honing my interviewing or reporting skills. If POLITICO came to me tomorrow and said, “Alex, you’ve got your pick: Want to be the next Senate reporter or our newest web designer?” I’m not sure which I’d choose.

Okay, that’s not true. I’d take the reporting gig in a heartbeat. But the thing is, building websites (and I assume plug-ins, web apps, and the like) is just so damn fun. It’s a puzzle, and I fucking love puzzles. I love that I have to enter in a sequence of letters, numbers and symbols into a document and see if I can get it to spit out exactly what I’m looking for – it’s like a really, really long password. It’s a challenge that doesn’t end – after I’ve won the first little battle, the next one comes along and I’m enamored by a new task. It’s why we never effing go to sleep.

Rest assured, I haven’t lost my desire to write and report – I hope you’ll see my byline in the near future. But there’s a new game in town that’s taking up more and more of my hobby time, so don’t be surprised if I continue to talk to you more and more about  Web design. And if you’re one of the many who knows far more than I, get ready to share that knowledge (thanks thus far to Nacin and Balter.)

UPDATE, Dec. 1: I should mention that while I still believe in the premise of this post, I’ve spent most days since it was published wishing I could program, develop, or data process — and trying to learn.

DOUBLE UPDATE, Dec. 1: Andy Boyle makes a good point that I hadn’t considered. Much of this post is based on the premise that writers should mainly stick to writing and let the programmers do the bulk of the programming. But what if there aren’t any programmers? Smaller news orgs may have none, and a journalist with a bit of programming experience is king in a world of no programmers.

There’s been considerable debate over the last couple of weeks about whether journalists should learn programming techniques and languages. Poynter hosted a chat on the subject, 10000Words put together a handy flowchart and others have joined the discussion.

On Tuesday, Andrew Nacin dropped my name as someone who falls on the yes-you-should-learn-programming-end-of-the-spectrum. While I appreciate Nacin’s mentioning me as a “living case study,” I do not think it’s necessary for today’s journalist to learn to program.

Before I explain why, let’s look at reasons you should learn to program. First, as MediaShift alludes to, we don’t really know what the media landscape will look like in 10 years. Is it possible that some level of programming will be folded into the standard responsibilities of the average journalist by that point? Maybe, though I doubt it. Second, it may provide you new career opportunities. Plenty of news organizations are starting to experiment with heaps of data and geo-location and the like, and being able to think journalistically while sifting through gigabytes of information may be your ticket to a cool new gig. And of course, the proverbial “why not?” reasoning. If you want to use your time to learn PHP or Ruby (or the WordPress Loop), be my guest. Just recognize it’s not for everyone.

Those points notwithstanding, programming simply is not a necessary (or useful) skill for today’s average journalist. Notice I did not say that programming is not a useful skill on its own; of course it is. The fact is, however, that programming requires too much time and energy to learn, while not providing an outlet for journalists to regularly use the knowledge. Sure, Brian Boyer and Matt Waite are make their living building awesome news applications. It’s just that not everyone can grow up to be them. The cops beat reporter in any city, USA should be cultivating sources, traversing the city, exposing corruption, and producing front page stories (and multimedia packages, maybe!), and that takes time and effort. For the good of the public and the reporter, these goals should trump those of learning to program.

Sure, that cops reporter could have a great idea for web application that automatically maps a location on a landing page when the local police or fire department tweets about an incident. But rather than having to build it all by him or herself, that’s a project to be tackled in conjunction with a dedicated developer. Those guys with the snarky T-shirts and binary jokes? Give them something to do. No need to steal their jobs. In this era of multitasking and convergence, it seems like people (and especially young journalists) are encouraged to learn how to do everything, and while initiative is good, that’s the wrong sentiment. Writers will produce the best written word, photographers will snap the best pictures, and programmers will build the best apps. That’s not going to change, so don’t give up being awesome at something so you can be insufficient at a lot of things.*

In short, if you want to be a programmer and build things, learn to program. If you want your byline on A1 tomorrow morning, focus on getting better at what it is you really want to do.

*Yes, with layoffs and the like, sometimes you will have to be the reporter and the photographer. But, that only works if you’re good enough to tackle both responsibilities, and you might not be if you spread yourself too thin with extraneous forays into too many sectors of the media industry.