Now that the Django Book is finally in the can, I'm mulling the idea of writing another book -- this time, a book about online journalism. In the past two years, I've been to (way too) many journalism-related events and conferences trying to spread the good word about 'journalism via computer programming,' and I've detected a strong, I daresay furious, demand, from journalists at all levels in the org chart, for information about this new form of journalism. Higher-ups want to know why they should employ programmers; middle managers want to know how to find them and how to treat them; and working journalists want to learn these skills and strategies. The problem is that I can't point them anywhere for in-depth information. This book would attempt to solve that.
I want to take a shot at writing a manual, a manifesto, a practical guidebook to this emerging discipline of database-driven Web journalism. It would be a combination of high-level strategy and low-level technique, probably split cleanly into two parts (one for the suits, one for the non-suits).
That's about all the thought I've given to this idea. What do you think? If you're a journalist (or even not), is this something you'd be interested in?"
I'm wondering where the manifesto is on programming-driven university teaching. As in, why does all of the software that's supposed to make it easier to distribute electronic documents and create classroom spaces STINK?
And, can Zotero and archive.org make it work?
Or, can Yale figure it out?