“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.

— via Matt Waite & Michelle Minkoff

A few thoughts on ‘The Social Network’

Just saw it. Some reflections are below:

  1. Is the genesis of Facebook and the Winklevoss’ lawsuit not the greatest testament to Matt Waite’s ‘demos, not memos‘ advice? Without being an expert on intellectual property nor researching the intricate details of the suit (for another time), Zuckerberg appears to be the de facto winner just by building the fucking thing. As Aaron Sorkin (writer crush) says in the screenplay, “If you guys were the inventors of Facebook, you’d have invented Facebook.” Put simply: If you have an idea, turn it into something tangible. Or if you’re like me and can’t program, get a friend who can and build it together.
  2. I’m a sucker for a good story (and I recognize that much of the movie’s truth is stretched) but I was really struck by the implicit power and opportunity in Facebook’s beginnings. A few 20-year-old kids in a dorm room started to build something and it ended of dramatically changing the world. College kids drinking beer and riffing on ideas. That’s me –(okay, a few months ago.) But it’s not people we see on TV or read about anymore. It is not at all a stretch to say that the people I’ve come into contact with or communicate with daily may be the creators of the next big thing in media and technology. It always used to be ‘other people.’ Not anymore.
  3. Once again setting aside the film’s fictional insinuations about how Facebook was built as one big plot to fit in and get girls, it does a good job of telling the truth about why technology matters. Digital tools help us improve our physical lives, which we tend to forget are still very much analog. The feeling you get when you relive a fond memory by looking through your old Facebook photos is quite literally an analog impulse being triggered by your brain and nervous system. Sure, you could experience that memory without the photo, but the photo makes it more vivid. The digital technology improves your analog world. (By the way, check the title tag of this blog’s homepage. I’ve been sitting on this idea for a while and really ought to write more about it.)

There is certainly much more to say, but that comes later. See the movie. Reactions have been mixed and polarized, but Sorkin makes you think – and you’ve got to love a story that makes you do some serious reflecting.

Should journalists learn programming?

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.