February 2003 | ||||||
Sun | Mon | Tue | Wed | Thu | Fri | Sat |
1 | ||||||
2 | 3 | 4 | 5 | 6 | 7 | 8 |
9 | 10 | 11 | 12 | 13 | 14 | 15 |
16 | 17 | 18 | 19 | 20 | 21 | 22 |
23 | 24 | 25 | 26 | 27 | 28 | |
Jan Mar |
My Topics:
k-log (66)
radio (56)
blogging (50)
RSS (46)
politics (36)
knowledge-management (34)
business (32)
topics (30)
tools (25)
software (25)
trackback (20)
google (17)
community (17)
shrub (15)
java (15)
humour (15)
metadata (14)
culture (14)
XML (13)
corruption (13)
XFML (12)
microsoft (12)
Gulf War II (12)
collaboration (12)
American culture (12)
XTM (11)
the middle east (11)
paolo (11)
information (11)
licensing (10)
learning (10)
publishing (9)
knowledge (9)
intranets (9)
blogplex (9)
outlining (8)
networking (8)
life (8)
Gurteen (8)
email (8)
wiki (7)
trust (7)
rant (7)
pax Americana (7)
palladium (7)
organisations (7)
open-source (7)
big media (7)
terrorism (6)
privacy (6)
PKP (6)
patents (6)
marketing (6)
law (6)
JIRA (6)
copyright (6)
broadband (6)
activeRenderer (6)
Wi-Fi (5)
tv (5)
the state (5)
spam (5)
sharing (5)
semantic-web (5)
security (5)
project management (5)
Lisp (5)
leaky pipes (5)
hope (5)
content-management (5)
consultancy (5)
CMS (5)
Business Journalling (5)
unemployment (4)
surveillance (4)
start-up (4)
programming languages (4)
pigopoly (4)
pagerank (4)
P2P (4)
leadership (4)
identity (4)
ideas (4)
groove (4)
Frontier (4)
connections (4)
career (4)
aggregators (4)
website (3)
warblogging (3)
visualization (3)
the economy (3)
test (3)
telecomms (3)
teaching (3)
social-networking (3)
selling (3)
RSI (3)
RIPA (3)
research (3)
referrers (3)
Novissio (3)
multimedia conversations (3)
memory (3)
media (3)
london (3)
investment (3)
innovation (3)
IM (3)
history (3)
e-government (3)
drm (3)
daypop (3)
communication (3)
Amazon (3)
XSLT (2)
xml-rpc (2)
XKM (2)
workflow (2)
words of wisdom (2)
webservices (2)
visibility (2)
UNL (2)
test topic (2)
tacit knowledge (2)
strategy (2)
storytelling (2)
spamblocking (2)
search tools (2)
Ryze (2)
RDF (2)
productivity (2)
PingBack (2)
organisational-development (2)
opml (2)
MovableType (2)
metalogue (2)
listening (2)
knowledge metrics (2)
information-overload (2)
InfoPath (2)
IE (2)
health (2)
hardware (2)
gpl (2)
faceted classification (2)
explicit knowledge (2)
European Union (2)
environment (2)
enron (2)
effectiveness (2)
edublogging (2)
Creative Commons (2)
CoP (2)
conferences (2)
bots (2)
big oil (2)
wizards (1)
Web Services Architecture (1)
UK culture (1)
transclusion (1)
TKP (1)
the-game (1)
text-analysis (1)
symantec (1)
structure (1)
stress (1)
State of fear (1)
stability (1)
socialtext (1)
sfa (1)
sensuality (1)
search-engines (1)
search heuristics (1)
s-l-a-m (1)
ROI (1)
respect (1)
quotations (1)
Process logging (1)
presentations (1)
PIM (1)
patterns (1)
ontology (1)
obituaries (1)
neighbourhood (1)
multi word topics (1)
morals (1)
manifestos (1)
M$ (1)
liberty (1)
kcafe (1)
jobs (1)
Italy (1)
issue tracking (1)
hypertext (1)
game-theory (1)
gadgets (1)
future-publishing (1)
FOAF (1)
films (1)
fibre (1)
failing fast (1)
faceted browsing (1)
enterprise streaming (1)
e-learning (1)
Dynamic DNS (1)
Dublin Core (1)
dns (1)
dieting (1)
dhtml (1)
deep-linking (1)
CyberWar (1)
CRM (1)
creativity (1)
conversation (1)
conflict (1)
complexity (1)
competition (1)
Colonising Space (1)
brands (1)
boycott (1)
bookmarklet (1)
backlinking (1)
annoyances (1)
algorithms (1)
agents (1)
adverts (1)
accessability (1)
academia (1)
Blogroll:
[Macro error: Poorly formed XML text, we were expecting . (At character #172.)]Recent Items:
3/27/03 |
|
3/27/03 |
|
3/27/03 |
|
3/26/03 |
|
3/26/03 |
|
3/26/03 |
|
3/26/03 |
|
3/25/03 |
|
3/24/03 |
|
3/24/03 |
|
3/23/03 |
|
3/23/03 |
|
3/19/03 |
|
3/19/03 |
|
3/18/03 |
|
3/18/03 |
|
3/18/03 |
|
3/18/03 |
|
3/18/03 |
|
3/18/03 |
|
3/18/03 |
|
3/17/03 |
|
3/17/03 |
|
3/17/03 |
|
3/17/03 |
|
3/13/03 |
This work is licensed under a
Creative Commons License.
Lisp really is a fascinating language. When I read Paul Graham talking about Arc and CLOS thus:
I personally have never needed object-oriented abstractions. Common Lisp has an enormously powerful object system and I've never used it once. I've done a lot of things (e.g. making hash tables full of closures) that would have required object-oriented techniques to do in wimpier languages, but I have never had to use CLOS.
At first I was inclined to dismiss it, after all lots of people denigrate OOP or say they don't need it. However already I can kind of see what he means.
I'm just running through tutorials at the moment, messing with functions and closures and messing with lists of functions and lists of data and... Well, lets just say it's opening some new pathways.
I still like Java, I'm still happy to code in Java, but I'm definitely enjoying Lisp and wonder about where it might take me.
Interesting, I just post about Wiki and here I read that the SocialText crew (Adina Levin, Ross Mayfield, Peter Kaminski, and Ed Vielmetti) are releasing a Wiki product of their own called NiceLittleWiki. I hope it will solve some of the current problems with Wiki software (ugliness, impossible media handling, lack of ability to format text when you need it, bad indexing, etc...).
SocialText may turn out to be one of the Purple Cows of KM. I await their next move with interest!
(With thanks to Terry for reminding me about SocialText)
I've been reading In Praise of the Purple Cow in which the author, Seth Godin, proposes that, in order to be truly successful, a product must be remarkable. His claim is that being very good is also failure. These days everyone is good or very good, you have to be remarkable to stand out and get the notices (good and bad).
The purple cow idea jives very much with what I've read of Gary Hamel's notion of how revolutionary approaches create new markets and deliver profits. Unless you also invest in new purple cows then building upon success is the road to stagnation. Ask AOL, Palm and Yahoo. This idea feels right to me.
Which lead me to thinking about knowledge management products and how so many of them are good, but hardly remarkable. Personal Brain is a remarkable product which was never exploited. The Wiki idea was remarkable, but none of the Wiki software I've used has been. In fact when I think about it, the whole field of KM is dominated by the idea of being good enough.
For example OpenText Livelink is a very successful KM product. Which gives you some idea of the state of that market. Livelink is a well-dressed document management system. Hardly innovative, definitely not purple cow territory. But it's been successful. Why is that?
I think the answer is partly about OpenText being an aggressive sales driven company, partly that the KM market is dominated by large, conservative, corporations, and partly because the whole market is ripe, waiting for a real purple cow.
Can anyone say "Moo!?!"