![]() |
Monday, September 02, 2002 |
100 THINGS ABOUT DEWAYNE MIKKELSON 1. I was born in San Diego, California. 8:20:33 PM ![]() |
The Intranet as Living Community. James provides a quick summary of, and pointers to, a well written strategic white paper on intranet design. [Blunt Force Trauma] 2:35:21 PM ![]() |
Computer Folkore. Computer FolkoreSaturday I attended the Con José panel on "Computer Folklore: Tales from the Geekside," featuring Eric Raymond, Chris Garcia, Tom Galloway, Brett Glass, and Corey Cole. Aside from a brief discussion of the first chain letter (an MIT student did it!) it wasn't what I'd expected, though that's OK. There are some good sources here, and even here. Computer folkore is, by the way, a genuine folkloric academic study, despite much of the humor involved. The panel was well attended, and amusing, but I'd guess about a half hour was spent in geek nostalgia, in the form of "my hardware is older than yours." The other version of this (and the two are often combined) is "my hardware is faster/more powerful/better than yours." This gives me the perfect opportunity to post the ultimate riposte to both debates, gleaned from UseNet, and as far as I know first posted by Christopher Lishka in May 1993 to both rec.humor.funny and comp.sys.mac.???. Thanks Christopher, wherever you are. [Instructional Technology] 2:27:51 PM ![]() |
Live Journal SIG. Live Journal SIGFriday morning at ConJosé I attended a Special Interest Group set up by a few Live Journal users. I've looked at Live Journal before; of all the various web log systems it seems to be the one most focused on community in the sense of creating communities via links to like minded Live Journal members, or "friends," as Live Journal would have it, and a comment system. Live Journal struck me as a good system to introduce undergraduates in introductory composition classes to writing for the web as a way of getting them to write and to think critically about writing as well as just becoming comfortable with writing as a habit. Most, but not all, of the Live Journal users are creating journal-like pages. Live Journal is a free service, though they encourage users to support Live Journal ($25.00/year) by offering extra services. It's open source as well. There are even a variety of clients, for pretty much any OS you'd want, to use in posting if you don't want to rely on a browser and web-based posting. The FAQs are here. It includes the usual structural devices, like chononological based postings, with the newest at the top, a calendar for access to the automatic archives, and various ways of editing and deleting and controlling access to the journal. Listening to the others at the SIG, I was particularly struck by a few observations. These are my observations, and in no way reflect on those Live Journalists referred to, or linked to. I'm sure I'm getting things entirely wrong in some way. They were both helpful and patient in answering my questions, so I expect some kind soul will straighten me out. In particular, The_ogre, Firecat, Wrapper, Isabeau, Rmjwell, Rowanf. In no particular order then, here are some random observations about Live Journal, based on my admittedly small sampling from the SIG, and some browsing: |
Groove strategy disussion. Joel Spolsky's worthreading essay on platforms generated a lot of discussion during the weekend. I'm still reading and digesting all of it. Some interesting threads on Joel's forum discussing the essay. On their weblogs Brian Jepson, Justin Rudd and Krzysztof Kowalczyk agree with Joel and are expressing strong doubts regarding Groove's strategy. Dave Winer points to an essay from 1996 explaining why Groove can't bet exclusively on being a platform and Alexis Smirnov writes : So do I think Joel's article is wrong? No, it simply fails to capture the real issue with Groove - there are two different views of "Groove Platform". One is being offered by Groove Inc. and another is wanted by ISVs. Groove Inc. defines the platform as Runtime plus Transceiver. Want to build on the Groove Platform - write a Groove Tool. Most ISVs define the platform as Runtime. Period. Most of the people thinking of integrating Groove's collaboration capabilities only want the Runtime. This is why Joel's analysis of cost/benefit of integrating Groove with CityDesk is right on the money - it illustrates the Groove/ISV gap. [Jeroen Bekkers' Groove Weblog]10:58:24 AM ![]() |
WinAmp 3. I've seen some people bitching about new WinAmp 3 but I like it. Free-form skins are awesome. Check out Timepiece skin. I'll probably settle for something clean and functional in the end but it's so much fun checking out all those crazy, beautifully designed skins. WinAmp might not look like much but in my opinion it teaches a few important lesson in software developement and marketing. WinAmp is a platform. WinAmp isn't just a music (and now video) player, it's a platform. All the user-contributed skins, visualization components help WinAmp fend off competition, even from those who can include competing player in the OS itself. WinAmp is not only useful, it's also desireable. When designing stuff, including software, the first step is to design something that is useful and functional. But when your competition's stuff is as functional as yours, you have to do better, you have to compete in desirability. Apple is a good example: their iPod doesn't play mp3 better than other players but it does look cool and that allows Apple charge for it more. WinAmp also does a lot of things that don't contribute much to functionality but a lot to desirability: tasteful splash screen with a reference to a recent boxoffice hit, visualizations, skins, animated "about box". WinAmp is masterfully marketed. Take a careful look at WinAmp website. It has it's own, distinctive voice. You won't find there cliched market speak ("our product is leading blah, blah..."). Web site is well designed (it's both tasteful and functional). It has forums so that people can talk about their products. It has plenty of documentation. While this exact style might not be appropriate for every software company, many could learn a lot from guys at WinAmp. Watch and learn. [Krzysztof Kowalczyk's Weblog]10:57:32 AM ![]() |
Why the Tivo / Replay Lawsuits are Futile. Why the Tivo / Replay Lawsuits are Futile[The FuzzyBlog!] 10:15:20 AM ![]() |