More ideas about ideas: Given my current interest in intellectual gardening rather than architecture, in allowing ideas to emerge rather than trying to generate them by a brute-force attack, I am reconsidering the way I have historically used my blogs, and wondering whether there’s not a better path to intellectual substance than the one I’ve been following.

This has been my M.O. going back to the relatively early days of Text Patterns, when I was working on The Pleasure of Reading in an Age of Distraction: Use the blog to generate and try out ideas, get feedback from readers, develop the ideas a little further … and then put on the brakes. But why did I put on the brakes? Because I knew that I was getting close to the point at which there would be so much of the book’s contents online that a publisher wouldn’t want to buy it. And so the idea-generating stage of the project would effectively come to an end.

Not altogether, of course; I could still write in notebooks or sketch ideas or whatever. But two things were missing: the felt need in writing a public post to achieve at least some minimal level of coherence, and the feedback from readers. Moreover, when you’ve been generating ideas using a particular method and then are forced to switch to another one, you tend to lose momentum. So effectively I found myself working with the ideas that I had generated to that point in the project — even when I didn’t feel that I had explored my chosen topics as thoroughly as I would have liked. And this happened more than once, most recently with my idea for a book on what I called Anthropocene theology.

So in these situations the limits and boundaries of my projects are set, not by the inner logic and impetus of those projects, but by the preferences of the publishing industry. But that’s a superficial take. Why, after all, should I allow the publishing industry to set those boundaries? Because in my line of work the highest-denomination currency is the book. I have my current job because of publishing books — Baylor simply would not have sought me out and hired me had I not been able to list several books on my CV.

Put it this way: If I had never blogged a single word I would have precisely the same job I have now; if I had blogged millions of words without publishing books I would not have a job.

But, you may say, at this point in my career why don’t I just do what I want? I have tenure; I have no administrative ambitions (indeed, just the reverse); I am a Distinguished Professor and there’s no such thing as an Extremely Distinguished Professor or Sun-God Professor. If I am feeling the demands of the publishing world as a heavy yoke why not just throw it off?

Well, I might. But I hesitate for two reasons, or maybe it’s one reason with two parts.

  1. My profession has never figured out what to do with online writing, except for a few peer-reviewed online journals. It is still devoted to finished products — and vetted products too, despite the manifest problems with peer review. Scholars will cite a dozen mediocre peer-reviewed published papers before they’ll cite even the most brilliant blog post.
  2. And working to the established standards of my profession is, as I have noted, what got me my current position, so that I can’t help feeling that if I were to strike out into unfamiliar writing territory I wouldn’t be keeping the implicit contract I made when I took this job.

So if I were to do the thing I am contemplating — pursue big intellectual projects all the way to their completion here on this blog — my university’s administrators would be unhappy, the publishers who want to publish my stuff would be unhappy, my magnificent literary agent would be unhappy, and some part of me would be unhappy.

But what if, by following SOP for my profession, I limit my ability to think? What if I curtail the development of ideas and end up fitting them into familiar boxes rather than following them to surprising and new and fascinating places? Isn’t that a heavy price to pay for professional adequacy?

More on all this in the next post.