Ah. I’d like to have an argument, please.

I’m living in a software-oriented version of that Monty Python sketch that begins, “I’ve come for an argument.” Wilfried always accused me of being a software critic, a term I have resisted in that a critic is not usually understood to also be a practiser. But perhaps it’s an appropriate term for rattling around digging […]

amateur personal information archaeology

Today I had a fun surprise digging out an old notebook of mine from a box that had been in my mother’s keeping. It dates through the summer of 2003, after my introductory whirl on the conference circuit with Gonzo Collaborative Mapping on the Semantic Web. At the end it overlaps with the “Crystalpunk Notebook” […]

a northern european tour

we lurked on the beer track mostly at foafcamp, but i visited the quick presentation sessions and did a braindump on geopolitical foaf, some of the socio-political networking projects that we’ve come across in california, some using foaf overtly, others with cotangent aims.
Most enjoyed, i think, graham klyne’s presentation on description logics in literate haskell, […]

attempt a literate project

i decided to use Class::RDF as a small test case for what a more ‘literate’ project and programming behaviour might be. a small collection of files, rss feeds of cvs commit notes and code journals written on irc, a DOAP file, some beautiful code coverage reports made by Devel::Cover.
imagining a wiki-like interface, to code, to […]

annotation and literate programming

Later i talked to dngnand about journalling, and he showed me a hidden blog where his cvs commit notes are made available in html and RSS. We also talked about literate programming, and his idea of using wiki markup as a way to write literate programs. i enjoyed reading knuth’s original article on literate programming, […]

journalling

bugfixing indyvoter drove me to crazed thoughts of conversational development methods: of consensus code generation without becoming a slave to formalisms or change control regimes. we all wander down paths of reasoning, change APIs, leaving no breadcrumbs on the onramp.
i didn’t have to invent a development methodology: i stole one from the preface to Tom […]