Tag Archives: Matt Mullenweg

Development and Quality: Reply to Agile Diary

Former WiZiQ product manager Vikrama Dhiman responded to one of my tweets with a full-blown blogpost, thereby giving support to Matt Mullenweg‘s point that microblogging goes hand-in-hand with “macroblogging.”

My tweet:

enjoys draft æsthetics yet wishes more developers would release stable products. / adopte certains produits trop rapidement.

Vikrama’s post:

Good Enough Software Does Not Mean Bad Software « Agile Diary, Agile Introduction, Agile Implementation.

My reply:

“To an engineer, good enough means perfect. With an artist, there’s no such thing as perfect.” (Alexander Calder)

Thanks a lot for your kind comments. I’m very happy that my tweet (and status update) triggered this.

A bit of context for my tweet (actually, a post from Ping.fm, meant as a status update, thereby giving support in favour of conscious duplication, «n’en déplaise aux partisans de l’action contre la duplication».)

I’ve been thinking about what I call the “draft æsthetics.” In fact, I did a podcast episode about it. My description of that episode was:

Sometimes, there is such a thing as “Good Enough.”

Though I didn’t emphasize the “sometimes” part in that podcast episode, it was an important part of what I wanted to say. In fact, my intention wasn’t to defend draft æsthetics but to note that there seems to be a tendency toward this æsthetic mode. I do situate myself within that mode in many things I do, but it really doesn’t mean that this mode should be the exclusive one used in any context.

That aforequoted tweet was thus a response to my podcast episode on draft æsthetics. “Yes, ‘good enough’ may work, sometimes. But it needs not be applied in all cases.”

As I often get into convoluted discussions with people who seem to think that I condone or defend a position because I take it for myself, the main thing I’d say there is that I’m not only a relativist but I cherish nuance. In other words, my tweet was a way to qualify the core statement I was talking about in my podcast episode (that “good enough” exists, at times). And that statement isn’t necessarily my own. I notice a pattern by which this statement seems to be held as accurate by people. I share that opinion, but it’s not a strongly held belief of mine.

Of course, I digress…

So, the tweet which motivated Vikrama had to do with my approach to “good enough.” In this case, I tend to think about writing but in view of Eric S. Raymond’s approach to “Release Early, Release Often” (RERO). So there is a connection to software development and geek culture. But I think of “good enough” in a broader sense.

Disclaimer: I am not a coder.

The Calder quote remained in my head, after it was mentioned by a colleague who had read it in a local newspaper. One reason it struck me is that I spend some time thinking about artists and engineers, especially in social terms. I spend some time hanging out with engineers but I tend to be more on the “artist” side of what I perceive to be an axis of attitudes found in some social contexts. I do get a fair deal of flack for some of my comments on this characterization and it should be clear that it isn’t meant to imply any evaluation of individuals. But, as a model, the artist and engineer distinction seems to work, for me. In a way, it seems more useful than the distinction between science and art.

An engineer friend with whom I discussed this kind of distinction was quick to point out that, to him, there’s no such thing as “good enough.” He was also quick to point out that engineers can be creative and so on. But the point isn’t to exclude engineers from artistic endeavours. It’s to describe differences in modes of thought, ways of knowing, approaches to reality. And the way these are perceived socially. We could do a simple exercise with terms like “troubleshooting” and “emotional” to be assigned to the two broad categories of “engineer” and “artist.” Chances are that clear patterns would emerge. Of course, many concepts are as important to both sides (“intelligence,” “innovation”…) and they may also be telling. But dichotomies have heuristic value.

Now, to go back to software development, the focus in Vikrama’s Agile Diary post…

What pushed me to post my status update and tweet is in fact related to software development. Contrary to what Vikrama presumes, it wasn’t about a Web application. And it wasn’t even about a single thing. But it did have to do with firmware development and with software documentation.

The first case is that of my Fonera 2.0n router. Bought it in early November and I wasn’t able to connect to its private signal using my iPod touch. I could connect to the router using the public signal, but that required frequent authentication, as annoying as with ISF. Since my iPod touch is my main WiFi device, this issue made my Fonera 2.0n experience rather frustrating.

Of course, I’ve been contacting Fon‘s tech support. As is often the case, that experience was itself quite frustrating. I was told to reset my touch’s network settings which forced me to reauthenticate my touch on a number of networks I access regularly and only solved the problem temporarily. The same tech support person (or, at least, somebody using the same name) had me repeat the same description several times in the same email message. Perhaps unsurprisingly, I was also told to use third-party software which had nothing to do with my issue. All in all, your typical tech support experience.

But my tweet wasn’t really about tech support. It was about the product. Thougb I find the overall concept behind the Fonera 2.0n router very interesting, its implementation seems to me to be lacking. In fact, it reminds me of several FLOSS development projects that I’ve been observing and, to an extent, benefitting from.

This is rapidly transforming into a rant I’ve had in my “to blog” list for a while about “thinking outside the geek box.” I’ll try to resist the temptation, for now. But I can mention a blog thread which has been on my mind, in terms of this issue.

Firefox 3 is Still a Memory Hog — The NeoSmart Files.

The blogpost refers to a situation in which, according to at least some users (including the blogpost’s author), Firefox uses up more memory than it should and becomes difficult to use. The thread has several comments providing support to statements about the relatively poor performance of Firefox on people’s systems, but it also has “contributions” from an obvious troll, who keeps assigning the problem on the users’ side.

The thing about this is that it’s representative of a tricky issue in the geek world, whereby developers and users are perceived as belonging to two sides of a type of “class struggle.” Within the geek niche, users are often dismissed as “lusers.” Tech support humour includes condescending jokes about “code 6”: “the problem is 6″ from the screen.” The aforementioned Eric S. Raymond wrote a rather popular guide to asking questions in geek circles which seems surprisingly unaware of social and cultural issues, especially from someone with an anthropological background. Following that guide, one should switch their mind to that of a very effective problem-solver (i.e., the engineer frame) to ask questions “the smart way.” Not only is the onus on users, but any failure to comply with these rules may be met with this air of intellectual superiority encoded in that guide. IOW, “Troubleshoot now, ask questions later.”

Of course, many users are “guilty” of all sorts of “crimes” having to do with not reading the documentation which comes with the product or with simply not thinking about the issue with sufficient depth before contacting tech support. And as the majority of the population is on the “user” side, the situation can be described as both a form of marginalization (geek culture comes from “nerd” labels) and a matter of elitism (geek culture as self-absorbed).

This does have something to do with my Fonera 2.0n. With it, I was caught in this dynamic whereby I had to switch to the “engineer frame” in order to solve my problem. I eventually did solve my Fonera authentication problem, using a workaround mentioned in a forum post about another issue (free registration required). Turns out, the “release candidate” version of my Fonera’s firmware does solve the issue. Of course, this new firmware may cause other forms of instability and installing it required a bit of digging. But it eventually worked.

The point is that, as released, the Fonera 2.0n router is a geek toy. It’s unpolished in many ways. It’s full of promise in terms of what it may make possible, but it failed to deliver in terms of what a router should do (route a signal). In this case, I don’t consider it to be a finished product. It’s not necessarily “unstable” in the strict sense that a software engineer might use the term. In fact, I hesitated between different terms to use instead of “stable,” in that tweet, and I’m not that happy with my final choice. The Fonera 2.0n isn’t unstable. But it’s akin to an alpha version released as a finished product. That’s something we see a lot of, these days.

The main other case which prompted me to send that tweet is “CivRev for iPhone,” a game that I’ve been playing on my iPod touch.

I’ve played with different games in the Civ franchise and I even used the FLOSS version on occasion. Not only is “Civilization” a geek classic, but it does connect with some anthropological issues (usually in a problematic view: Civ’s worldview lacks anthro’s insight). And it’s the kind of game that I can easily play while listening to podcasts (I subscribe to a number of th0se).

What’s wrong with that game? Actually, not much. I can’t even say that it’s unstable, unlike some other items in the App Store. But there’s a few things which aren’t optimal in terms of documentation. Not that it’s difficult to figure out how the game works. But the game is complex enough that some documentation is quite useful. Especially since it does change between one version of the game and another. Unfortunately, the online manual isn’t particularly helpful. Oh, sure, it probably contains all the information required. But it’s not available offline, isn’t optimized for the device it’s supposed to be used with, doesn’t contain proper links between sections, isn’t directly searchable, and isn’t particularly well-written. Not to mention that it seems to only be available in English even though the game itself is available in multiple languages (I play it in French).

Nothing tragic, of course. But coupled with my Fonera experience, it contributed to both a slight sense of frustration and this whole reflection about unfinished products.

Sure, it’s not much. But it’s “good enough” to get me started.

My Blogging Life


I just finished what might be one of my longest blogposts, ever:

PHP #1: Austin, TX (USA) « The Compulsive Pedestrian

I guess I had a lot to say… 😎

It’s on a new topical blog I created. That blog deals with what I now like to call “carfree living.” I was originally calling this “carless living” but “carfree” sounds better, for obvious reasons. 😉

I’ve been using that blog to talk about places that I know and that I perceive to be pedestrian-friendly or pedestrian-hostile. Hopefully, some people will connect to some of what I say about those places and eventually leave me comments. (Hint, hint! 😀 )

Actually, I’ve been receiving a decent number of comments through my blogs, recently. In fact, one blogpost became something of a forum thread, thanks in part to Carl Dyke who recently became a blogger. I “met” Carl on the anthro group blog Savage Minds, where Kerim Friedman and others have expressed their desire for more connections between anthro-friendly blogs.

For reasons which might not be entirely surprising, my blogpost comparing Texan and Albertan cities is getting a decent level of attention, especially from Edmontonians. In fact, it should be featured as a guest column on a community site. I even started looking at Edmonton as a place where I could live in the not-too-distant future!

Some of my other blogging activities are helping me get or keep in touch with diverse people. A coffee roaster, a former student, some local friends in both Montreal and Austin…

Though I tend not to care so much, I notice that visits to my main blog have been on the rise, in the past few months. If this tendency is maintained, I might get beyond my previous record of 5,867 visits in a month (in February, 2007). Through the rest of 2007, monthly visits to this blog ranged between 3,500 and 4,500, with a dip to 2,800 in June. (Yeah, I know. Fas-ci-na-ting.)

What’s more, I think that a larger proportion of visits to my blog are to posts I personally find interesting (as opposed to some silly posts which get lots of hits because their titles).

I’m now a bit more familiar with the new interface for WordPress.com blogs. Though the change was probably not visible to readers, the changes are rather extreme. What I find sad is that several features went away with the update: realtime wordcount, list nesting, automatic answerlinks, drag-and-drop widget management, and comma-separated categories. None of these features was really essential and the last one had good reasons to go, but it still implies a major adaptation. In fact, as much as I enjoy blogging on WordPress (and as grateful as I am to have access to a feature-full free blog host), I take issue with some of the ways Matt Mullenweg and his Automattic crew have treated WordPress.com users, on occasion. In this case, it would have been much easier if they had described the changes in advance, providing some documentation to enable a smooth transition. I know the update’s focus was on WordPress installed on people’s servers (i.e., not on blogs hosted on WordPress.com). But it does make me feel like a second-class citizen, which may not be what Automattic wants.

Thanks in part to changes in the way WordPress.com handles tags and categories, I’ve been able to clean up some of my categories for this blog. It’s still pretty much a mess, I know. But it’s much closer to being manageable than it was. And I notice the difference quite easily.

I also shuffled some widgets around my blog design, which was surprisingly difficult because of the changes in the WordPress.com interface. I think my blog is just a bit cleaner than it was.

The fact that my daily average blogpost count has increased in the past several days is partly due to a decision of mine to do more things through my blogs. I eventually realized what part blogging had to play in my life and these past several days were an occasion for me to use blogging as a kind of release. There really is something quite therapeutic about blogging.

One thing it might mean, though, is that this blogging spree will taper off relatively soon. As I’m preparing to move for the 22nd time since December, 2000, it’ll probably be best if I focus on other things besides blogging.

The cool thing is, blogging allows for this kind of behavior. The only thing a decrease in my blogging activities might mean is a drop in readership. But I care very little about hits and there are other ways for me to get in touch with people.

New/Old Media: NYT Groks It

As an obvious example of “Old Media” in the U.S., The New York Times is easy to criticize. But the paper and the media company have also been showing signs that maybe, just maybe, they are home to people who do understand what is happening online, these days.

Back in September 2007, for instance, the NYT decided to make its content freely available. While The Times wasn’t the first newspaper to free its content, the fact that the “newspaper of record” for the United States went from a closed model (TimesSelect) to an open one was quite consequential. In fact, this NYT move probably had an impact on the Wall Street Journal which might be heading in a similar direction.

The Times‘s website also seems to have progressively improved on the blogging efforts by some of its journalists, including composer and Apple-savvy columnist David Pogue.

Maybe this one is just my personal perception but I did start to read NYT bloggers on a more regular basis, recently. And this helped me notice that the Times wasn’t as “stuffy and old” as its avid readers make it to be.

Possibly the silliest detail which has been helping me change my perception of the New York Times was the fact that it added a button for a “Single Page” format for its articles. A single page format is much more manageable for both blogging and archiving purposes than the multiple page format inherited from print publications. Most online publications have a “printer-friendly” button which often achieves the same goal as the NYT’s “single page” button yet, quite frequently, the printer format makes a print dialogue appear or is missing important elements like pictures. Not only is the NYT’s “Single Page” button a technical improvement over these “printer-friendly” formats but it also seems to imply that people at the Times do understand something about their online readers.

This “Single Page” button is in a box, with other “article tools” called “Print,” “Reprints,” and “Share.” The “sharing” features are somewhat limited but well-integrated. They do make it easy for some social networkers and bloggers to link to New York Times content.

FWIW, my perception of this grande dame of print publications is greatly influenced by my perception of the newspaper’s blog-friendliness.

Speaking of blog-friendly… The major news item making the New York Times Company seem even more sympathetic to bloggers is the fact that it has contributed to a round of funding which provided WordPress.com’s parent company Automattic with 29.5 M$.

Unsurprisingly, Automattic’s founder Matt Mullenweg blogged about the funding round. Candidly recounting the history of his company, Mullenweg whets our appetites for what may be coming next in WordPress and in other Automattic projects:

Automattic is now positioned to execute on our vision of a better web not just in blogging, but expanding our investment in anti-spam, identity, wikis, forums, and more — small, open source pieces, loosely joined with the same approach and philosophy that has brought us this far.

While some of these comments sound more like a generic mission statement than like a clear plan for online development, they may give us a glimpse of what will be happening at that company in the near future.

After all, chances are that integrating technologies will be one of the Next Big Things. In fact, some other people have seen the “social networking” potential of WordPress.com, though this potential is conceived through a perspective different from my original comments about WordPress.com’s network effect. Guess I’ll have to write a wishlist for WordPress.com features (including support for ubiquitous social networking, podcasting, and learning management).Still, what the funding announcement means to me has more to do with the integration of “Old Media” (print publications like The New York Times) and “New Media” (online services like WordPress and WordPress.com). As luck would have it, I’m not the only blogger who thinks about the positive effects this Old/New Media integration may have.

As an aside, to this Austinite and long-time sax player, Matt Mullenweg’s Texas and saxophone connections are particularly endearing. Good thing I’m not an investor because I would probably follow my gut feeling and invest in Automattic for such irrational reasons.

Ah, well…