Continuing from the discussion regarding intellectual practice, I've been talking with a number of people (my father in particular) about graduate school and the prospect of "bootstrapping" a scholarly practice using "new media," like blogging, and wiki making. I want to explore both my thoughts graduate school and bootstrapping with new media, and as you'd expect both of these ideas are rather intertwined. My initial gloss follows:

I've started to realize that, fundamentally, the questions I'm asking of the world and that I'm trying to address by learning more about technology, center on work and the meaning and process of working. Work lies at the intersection of the all the things that I seem to revisit endlessly: interfaces, collaboration technology, cooperatives and economics institutions, and open source software development. I'm not sure if I'm interested in work because it's the unifying theme of a bunch of different interests, or this is the base from which other interests spring.

I realize that this makes me an incredibly weird geek.

I was talking to caroline about our respective work environments, specifically about how we (and our coworkers) relocated (or didn't) for our jobs, and I was chagrined to realize that this novel that I've been working at (or not,) for way too long at this point spends some time revolving around these questions:

• How does being stuck in a single place and time constrain one agency to effect the world around them?
• What does labor look like in a mostly/quasi post-scarcity world?

Perhaps the most worrying thing about this project is that I started writing this story in late August of 2008. This was of course before the American/Financial Services economic crash that got me blogging and really thinking about issues outside of technology.

It's interesting, and perhaps outside the scope of this post, but I think it's interesting how since graduating from college, my "research" interests as they were, all work them into fiction (intentionally or otherwise.) I suppose I haven't written fiction about Free Software/open source, exactly, but I think there's a good enough reason for that. [1]

I'm left with two realizations. First, that this novel has been sitting on my plate for far too long, and there's no reason why I can't write the last 10/20 thousand words in the next few months and be done with the sucker. Second, I'm interested in thinking about how "being an academic" (or not) affects the way I (we?) approach learning more about the world and the process/rigor that I bring to those projects.

But we'll get to that later, I have writing to do.

[1]	I write fiction as open source, in a lot of ways, so it doesn't seem too important to put it in the story as well.

I've realized much to my chagrin that I haven't written a post on about the Awesome Window Manager in a long time. It's funny how window managers just fade into the background, particularly when they work well and suit your needs. Why then, does this seem so important to me and why am I so interested in this? Funny you should ask.

Tiling window managers aren't going to be the Next Big Thing in computing, and if they (as a whole) have an active user-base of more than say 10,000 people that would be really surprising. While I think that a lot of people would benefit and learn from using Awesome (or others), even this is something of a niche group.

As a result, I think something really interesting happens in the tiling window manger space. First, the project is driven by a rather unique driving force that I'm not sure I can articulate well. It's not driven by a desire of profit, and it's not driven by some larger Utopian political goal (as a lot of free software is). This is software that is written entirely for oneself.

That's the way most (ultimately) free software and open source projects start. A lot of emphasis in the community (and outside) is made on the next stage of the progress, where a project that was previously "for oneself" becomes something larger with broader appeal. Lets start with the git version control system which started because the kernel development team needed a new version control system, but in the past couple of years has become so much more, by way of phenomena like github and flashbake. The free software and open source worlds are full of similar examples: the Linux Kernel, Drupal, b2/WordPress, Pidgin/Gain, Asterisk, and so forth.

But Awesome, and the other tiling window managers will, likely as not never make this jump. There is no commercial competitor for these programs, they're never going to "breakthrough" to a larger audience. This isn't a bad thing, it just effects how we think about some rather fundamental aspects of software and software development.

First, if developers aren't driven by obvious "us versus them" competition, how can the software improve? And aren't there a bunch of tiling window mangers that compete with each other?

I'd argue that competition, insofar as it does occur, happens within a project, and within the developer rather than between projects and between developers. Awesome developers are driven to make Awesome more awesome, because there's no real competition to be had with Aqua (OS X window manger,) or other Kwin and Metacity (GNOME and KDE's window mangers), or even other alternate X11 window managers like OpenBox.

Developers are driven to "do better," than the people that preceded them, better than their last attempt, better than the alternate solutions provided by the community. Also, the principals of minimalism which underpins all of these window managers towards simple, clean, and lightweight code, inspires development and change (if not growth, exactly). This seems to hold true under anecdotal observation.

While there are a number of tiling window managers in this space, I'm not sure how much they actually compete with each other. I'd love to hear what some folks who use xmonad and StumpWM have to say about this, but it's my sense that the field of tiling window managers has more to do with other interests. Xmonad makes a point about the Haskel programing language. Stump is targeted directly toward emacs users and demonstrates that Lisp/Common Lisp is still relevant. Awesome brings the notion of a framework to window management, and seems to perfectly balances customizable with lightweight design. While Awesome is a powerful player in this space, I don't think that there's a lot of competition.

Second, if there's no substantive competition in this domain and if there's a pretty clear "cap" to the amount of growth, how are tiling window managers *not entirely pointless.*

I think there are two directions to go with this. First I think we're seeing some of the benefits of these window managers in other projects like xcb (a new library for dealing with X11) and freedesktop benefit both directly and indirectly from the work being done in the tiling window manager space. Similarly, Xmonad is a great boon to the Haskell community and cause (I suspect).

The other direction follows an essay I wrote here a few months ago about the importance of thinking about the capabilities of programing languages even if you're not a programmer because languages, like all sorts of highly technical concepts and tools create and constrain possibilities for all computer users, not just the people who ponder and use them. In the case of the tiling window manager, thinking about how the people who are writing computer programs is productive. In addition to the aforementioned thoughts about competition and open source.

So there we are. I'll be in touch.

I've been working a bit--rather a lot, actually--on getting myself ready to apply for graduate school (again) in a year to eighteen months, and one of the things that I'm trying to get figured out is the "why" question. Why go? Why bother? Questions like that. For starters, I hope to have some of the youthful angst regarding education knackered by the time I go back, and second, I think I'll be able to make the most of the experience. This post speaks to one part of this challenge: about what research is productive and worthwhile (that is, novel and original), and what research is by contrast merely an explanation of the obvious.

This is all predicated on the assumption that there's some sort of qualitative divide between the kind of causal observation and theoretical work that is what I do, (already), and "real work," productive work that productively contributes to a discourse. (Too young for impostor syndrome? unlikely!) Now this might be a ill conceived separation but, nevertheless the thought is on my mind.

The trains of thought:

• There's some fundamental difference between blagging and productive "knowledge production." Blogging is a practice that doesn't lead to systematic investigation, and thus, while interesting and a productive tool for the development of my thinking, it's a lousy end in and of itself.

  As I wrote that above paragraph, I remember that it resonated with a thought I've had about this website (in it's previous iterations) many years ago. Interesting.

• Fiction writing has (and continues) to be the most satisfying output of this impulse that I've been able to have thus far. While I do worry that my fiction isn't novel enough, that's a technical (eg. plot, setting, character) issue rather than a theoretical (eg. the science, and historiography) concern.

  Fiction writing also has a long publication cycle. My blog posts, from inception to posting, aren't particularly time intensive. Fiction, even/especially short stories require a bunch of extra time, and being able to immerse myself in a collection of ideas for a long time has a bunch of benefit.

  Also, there's a credential issue that I rather enjoy with-regards to Science Fiction. There's no degree that I could possibly want. I mean, sure, there are popular fiction writing programs, but that's not a requirement, and I suspect that I'll (try) to go to viable paradise sometime in the 2010s (or Clarion if I am somehow, ever, able to spare 6 grand and the ability to take 6 weeks off of my life), these would just be "for me," and there's nothing other that the quality of my work and the merit of my ideas that are between me and acceptance as a science fiction writer. That's really comforting, somehow.

• Most of us read literature of some sort, and talk about literary texts of one stripe or another, but I don't think that these activities necessarily make most of us literary critics. The art and project of literary criticism is something more. The difference between reading and talking about a text and practicing literary criticism is an issue of methodology. One of the chief reasons I want to go back to school is to develop an additional methodological tool kit, because my current one is a bit lacking. I'm pretty convinced that the difference between "thinking/doing cool things" and "doing/thinking important things," is largely an issue of methodology.

While I don't think this would short circuit the gradschool plans, but I think working to develop some sort of more rigorous methodological companion to the blogging process that goes beyond the general "so folks, I was thinking about foo so I'm going to tell you a story" (did I just give away my formula? Eep!)

In my post about my fact file I said that I was going to "try things out and see how it goes" before I posted code to see how things work in the system. Well, I think things are pretty stable (I haven't tweaked much), so I'm going to post my remember template, for the system described in that post.

(setq org-remember-templates
   '(("data" ?d "* %^{Title} %^g \n :PROPERTIES:\n :date:
       %^t\n :cit e-key: %^{cite-key}\n :link: %^{link}\n
       :END:\n\n %x %?"  "~/org/data.org")))`

If you want to tweak further, check out the relevant section of the org manual.

Enjoy and collect facts with abandon!