|
I had some interesting conversations with Andree Seu over the weekend. Afterward, I went surfing to see where she was referenced. It is strange to see a friend's work used as an example of rhetoric for a class on Rhetoric and Western Culture. Her work is quoted or copied widely enough that I have encouraged her to start a blog, if it doesn't interfere with her other contractual obligations. Good heavens, "work for hire"...Just saw that somewhere, perhaps on Instructional Technology. I remember the Intellectual Property contracts I disagreed with and edited the bejabbers out of, that claimed that anything I thought of while employed at X belonged to X, even if I developed the idea years later. (X was everything from Harvard Medical School to Digital Equipment Corporation and its clients.) I tried to leave most of those agreements in shreds, looking like those "declassified" government documents in which everything of interest between "Dear Sir" and "Respectfully Yours" was blacked out. |
|
Helpful notes on stakeholder interviews from Column Two. I first encountered these useful exercises when doing a technical review of Kulak and Guiney's Use Cases: Requirements in Context for Addison-Wesley. One of the ideas that I found especially valuable was interviewing the stakeholders who opposed the project, in order to find out what their objections were. This would make it possible to work the project to satisfy their requirements, which may have been overlooked in the original plans. Stakeholder interviews. I'm back working with the Area Health Service tomorrow. The next three days will consist entirely of stakeholder interviews, finished [Column Two] 1:06:00 PM |
|
This quotation (cited by Udell) gives a quick example of a translucent database. (Applying this might prove fruitful where I work.) For example, what if a police department needs to build a database of sexual-assault victims that lets them identify trends but hides personal information? You could use a translucent database where the first column is the hash of the victim's name, and the second column is a hash of their full address, and the third column is a hash of their block and street. You can now group incidents together by grouping entries with identical block hashes; you can see if the incidents refer to the same person by checking to see if those hashes are different.
More on translucent databases. A few weeks back I mentioned Peter Wayner's new book on Translucent Databases. Simson Garfinkel writes about it at more length in this oreillynet.com article: ... [Jon's Radio] 12:57:14 PM |
|
More about break reminder. I've had a couple of comments about my use of the Break Reminder software I mentioned in an earlier posting. These are to the effect that people think it would be quite disruptive to be interrupted so much, the you lose your flow, and that you are "on break" too much of the time to get anything useful done. These are all valid concerns. However for me, priority 1 is not to lose the use of my hands and that means managing my pain levels carefully. On bad days I use the settings that I indicated, on better days -- like today -- I step down a notch (4 minutes work time, 20 second micropauses, 12 micropauses to a rest break, 10 minute rest break). Even so it's not as bad as you might think. A micropause is not a telephone call, it does not involve a "thought interrupt." I can keep my flow and continue to think about what I am doing. For example I used a micropause a second ago to form this the though I have just written. Of course it's not the same as just typing away, but I can't do that or my pain levels get too high. Rest breaks are more likely to interrupt your flow, but on the lower setting I only get about one of those an hour. That's probably as long as I could flow usefully without a break anyway. In summary, yes adding these kind of breaks does impact on the amount of work you can do, yes it interrupts you to some degree but it it also keeps me working without excessive pain. And that's what it's all about! [Curiouser and curiouser!] 12:56:19 PM |
|
myOnlineLife. Wow - while I was on vacation, I missed the release of myRadio . "This Tool extends the Radio Userland aggregator from rss to any networked data (xml, html, soap, personalized services, etc), and any layout. It is exceedingly simple for developers to add functionality to the framework. The GUI ( screenshot ) is reminiscent of My Yahoo! and other server based personalization tools. The goal of this project is to very quickly bring all the functionality of server based personali... [The Shifted Librarian] 12:51:10 PM |
|
Blogging and Nineteenth Century Pamphlets. Blogging and Nineteenth Century Pamphlets
Doc Searls points to this journalistic gem from Tim Rutten of the Los Angeles Times. You need to register to experience the full joy of Rutten's "To Err Is Human, but to Think Out Loud," but the meat of his assertion is this bit: bloggers are basically a narcissistic throwback to an easily recognizable American type, the 19th century cranks who turned out mountains of self-published pamphlets.
I pontificated earlier about journalists not knowing their own history. Clearly, some of them don't really know nineteenth century literature either. Let's take a closer look at those nineteenth century pamphleteers, shall we? There's that crank Thoreau, with his nutty pamphlet "On Civil Disobedience," or that goofy Twain guy writing about the abuses of King Leopold in the Congo (1905 is twentieth century, technically, but still . . .), or that goofy Victorian Thomas Carlyle. Aside from scholarly obsessions with nineteenth century pamphlets as primary source documents about the lives and thoughts of everyday cranks as well as the hundreds of household names who were engineers, theologians, artists, poets, essayists, abolitionists and feminists, it's important to realize that pamphlets were published because they were popular. People, all kinds of people, read and wrote them. Sure, there were "cranks," but the vast majority of authors were quite serious, and were perceived that way. The pamphlets were written often enough by "names" to have inspired one of the most successful and expensive literary forgery operations ever, largely executed by one Thomas J. Wise. As a put-down, comparing bloggers to nineteenth century pamphleteers is less than effective, since so much of the intellectual life of the era was carried out via pamphlets, their publication in turn encouraged by the extensive correspondence between the authors, ultimately leading to several "schools" like the Transcendentalists in New England and the Tractarians in England. Both groups were strongly influenced by Milton, an avid pampleteer in the seventeenth century (writing, among other pamplets, Areopagitica on the freeedom of the press). Bloggers could do far worse in their search for a literary ancestor. [Instructional Technology]12:09:16 PM |
|
Ah, a medievalist: someone who actually knows something about rhetoric. Rhetoric of weblogs. 12:00:39 PM |
|
Check this out, especially in light of Bruce's metaphor for the vendor/user relationship: a rich kid (the user) and the supermodel (the vendor) trying to keep the kid around: The point is to make it harder to break up with me, the vendor, than it is to put up with my continual exploitation. There are basically six ways to do this. They get used in the information business all the time. Anyway check Bruce's article out. Thanks, Jim.
Sterling on Open Source. 11:42:47 AM |

