Tag Archives: troubleshooting approach

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.

Why Is PRI's The World Having Social Media Issues?

Some raw notes on why PRI’S The World (especially “The World Tech Podcast” or WTP) is having issues with social media. It may sound bad, for many reasons. But I won’t adapt the tone.

No offense intended.

Thing is, I don’t really care about WTP, The World, or even the major media outlets behind them (PRI, BBC, Discovery).

Reason for those notes: WTP host Clark Boyd mentioned that their social media strategy wasn’t working as well as they expected. Seemed like a nice opportunity to think about social media failures from mainstream media outlets.

My list of reasons is not exhaustive and it’s not really in order of importance.

Social media works best when people contribute widely. In other words, a podcaster (or blogger, etc.) who contributes to somebody else’s podcast (blog, etc.) is likely to attract the kind of mindshare afforded social media outlets. Case in point, I learnt about WTP through Erik Hersman because Afrigadget was able to post WTP content. A more efficient strategy is to actually go and contribute to other people’s social media.

The easiest way to do it is to link to other people, especially other blogs. Embedding a YouTube video can have some effects but a good ol’ trackback is so much more effective. In terms of attention economy, the currency is, well, attention: you need to pay attention to others!

Clark Boyd says WTP isn’t opposed to interacting with listeners. Nice… Yet, there hasn’t been any significant move toward interaction with listeners. Not even “letters to the editor” which could be read on the radio programme. No button to leave audio feedback. Listeners who feel they’re recognized as being interesting are likely to go the social media route.

While it’s a technology podcast, WTP is formatted as a straightforward radio news bulletin. “Stories” are strung together in a seamless fashion, most reports follow a very standard BBC format, there are very few “conversations” with non-journalists (interviews don’t count as conversations)… Such shows tend not to attract the same crowd as typical social media formats do. So WTP probably attracts a radio crowd and radio crowds aren’t necessarily that engaged in social media. Unless there’s a compelling reason to engage, but that’s not the issue I want to address.

What’s probably the saddest part is that The World ostensibly has a sort of global mission. Of course, they’re limited by language. But their coverage is even more Anglo-American than it needs to be. A far cry from Global Voices (and even GV tends to be somewhat Anglophone-centric).

The fact that WTP is part of The World (which is itself produced/supported by PRI, BBC, and Discovery) is an issue, in terms of social media. Especially given the fact that WTP-specific information is difficult to find. WTP is probably the one part of The World which is savvy to social media so the difficulty of finding WTP is made even more noticeable by the lack of a dedicated website.

WTP does have its own blog. But here’s how it shows up:

Discovery News: Etherized.

The main URL given for this blog? <tinyurl.com/wtpblog> Slightly better than <http://tinyurl.com/6g3me9> (which also points to the same place). But very forgettable. No branding, no notion of an autonomous entity, little personality.

Speaking of personality, the main show’s name sounds problematic: The World. Not the most unique name in the world! 😉 On WTP, correspondents and host often use “the world” to refer to their main show. Not only is it confusing but it tends to sound extremely pretentious. And pretention is among the trickiest attitudes in social media.

A strange dimension of WTP’s online presence is that it isn’t integrated. For instance, their main blog doesn’t seem to have direct links to its Twitter and Facebook profiles. As we say in geek circles: FAIL!

To make matters worse, WTP is considering pulling off its Facebook page. As Facebook pages require zero maintenance and may bring help listeners associate themselves with the show, I have no idea why they would do such a thing. I’m actually having a very hard time finding that page, which might explain why it has had zero growth in the recent past. (Those who found it originally probably had friends who were adding it. Viral marketing works in bursts.) WTP host Clark Boyd doesn’t seem to have a public profile on Facebook. Facebook searches for WTP and “The World Tech Podcast” don’t return obvious results. Oh! There you go. I found the link to that Facebook page: <http://www.new.facebook.com/home.php#/group.php?gid=2411818715&ref=ts>. Yes, the link they give is directly to the new version of Facebook. Yes, it has extra characters. No, it’s not linked in an obvious fashion.

That link was hidden in the August 22 post on WTP’s blog. But because every post has a link with “Share on Facebook” text, searching the page for “Facebook” returns all blogposts on the same page (not to mention the “Facebook” category for posts, in the right-hand sidebar). C’mon, folks! How about a Facebook badge? It’s free and it works!

Oh, wait! It’s not even a Facebook page! It’s a Facebook group! The difference between group and page seems quite small to the naked eye but ever since Fb came out with pages (a year or so ago), most people have switched from groups to pages. That might be yet another reason why WTP isn’t getting its “social media cred.” Not to mention that maintaining a Facebook group implies just a bit of time and doesn’t tend to provide direct results. Facebook groups may work well with preestablished groups but they’re not at all effective at bringing together disparate people to discuss diverse issues. Unless you regularly send messages to group members which is the best way to annoy people and generate actual animosity against the represented entity.

On that group, I eventually learn that WTP host Clark Boyd has his own WTP-themed blog. In terms of social media, the fact that I only found that blog after several steps indicates a broader problem, IMHO.

And speaking of Clark Boyd… He’s most likely a great person and an adept journalist. But is WTP his own personal podcast with segments from his parent entity or is WTP, like the unfortunately defunct Search Engine, a work of collaboration? If the latter is true, why is Boyd alone between segments in the podcast, why is his picture the only one of the WTP blog, and why is his name the domain for the WTP-themed blog on WordPress.com?

Again, no offence. But I just don’t grok WTP.

There’s one trap I’m glad WTP can avoid. I won’t describe it too much for fear that it will represent the main change in strategy. Not because I get the impression I may have an impact. But, in attention economy, “the squeaky wheel gets the grease.”

Oops! I said too much… 🙁

I said I don’t care about WTP. It’s still accurate. But I do care about some of the topics covered by WTP. I wish there were more social media with a modicum of cultural awareness. In this sense, WTP is a notch above Radio Open Source and a few notches below Global Voices. But the podcast for Global Voices may have podfaded and Open Source sounds increasingly U.S.-centric.

Ah, well…

Optimism From OLPC

To say the least, I’ve been ambivalent about the One Laptop Per Child project. And I was not alone in my OLPC discomfort.

But now, I feel optimistic. Not about the OLPC project. But because that project is enabling something important.

Continue reading Optimism From OLPC