http://nitpicker.pbwiki.com/ Nitpicker's positions on matters of interest to him and maybe to you. Your invite key is "Nitpicker's 77 Secret" en http://nitpicker.pbwiki.com/feedlogo.gif http://pbwiki.com/ PBwiki 3.7 support@pbwiki.com http://nitpicker.pbwiki.com/JustGo email.hidden@example.com (Richard Karpinski) Richard Karpinski edited JustGo Notice that the thumbnails amount to links but navigating among them is as simple as possible if one's hand is already on the mouse. We might also provide a way to navigate by keyboard. Suppose that each thumbnail had a one or two letter key, perhaps shown as semi-transparent large letters covering the thumbnail image. Then by using a meta-key, perhaps called LEAP, and possibly located below the space bar for convenient access by one's thumb, one might type the one or two letters thus moving the mouse cursor to the thumbnail and auto zooming into it. If one's hands were on the keyboard already, this would eliminate the 1.7 (?) second cost of moving a hand to the mouse.
===================================
Past here is an extended discussion with Nat Fast who is thinking about actually implementing a JustGo world. My comments are in italics. rhk, Nitpicker
For this first version I want to do as much as possible with only the mouse and no keys, buttons, or even mouse induced scrolling. If what I w]]> Sun, 18 May 2008 22:32:39 +0000 mod http://nitpicker.pbwiki.com/JustGo email.hidden@example.com (Richard Karpinski) Richard Karpinski edited JustGo This idea must be verified by user testing. There will be many ways to implement such auto zooming worlds, but any one will likely suffice to see if such a system is as pleasing to use as I hope. My current candidate for a convenient system in which this can be built is Sun's Lively Kernel. Online videos of two talks about Lively Kernel are available as a Google talk and as a session of EE380 at Stanford. Can you find another convenient way to implement such a scheme?
Notice that the thumbnails amount to links but navigating among them is as simple as possible if one's hand is already on the mouse. We might also provide a way to navigate by keyboard. Suppose that each thumbnail had a one or two letter key, perhaps shown as semi-transparent large letters covering the thumbnail image. Then by using a meta-key, perhaps called LEAP, and possibly located below the space bar for convenient access by one's thumb, one might type the one or two letters thus moving the mouse cursor to the thumbnail and auto zooming]]> Sun, 18 May 2008 22:30:09 +0000 mod http://nitpicker.pbwiki.com/Wikis+to+replace+forums email.hidden@example.com (Richard Karpinski) Richard Karpinski added Wikis to replace forums This is about improving the Get Satisfaction forum which was designed to provide customer support for software and other companies. You can see the original discussion there at http://getsatisfaction.com/satisfaction/topics/we_want_comments_about_our_new_comments_feature#

We should learn from the success of Wikipedia and create topic articles (at the top of each topic) to summarize and continually refine the best understanding of the topic. The original question/problem/whatever with its replies and comments constitutes the Talk page for the topic article.

The largely time sequenced replies and comments just make the topic LONGER. The gems of value get buried. The article at the top can get BETTER over time. That\'s a tremendous advantage.

Treat the article as in a wiki so damage can be reverted and attribution for changes is hidden in the history. You can make the history a third part of the topic at the bottom if you like.

The forum style replies and comments should, I feel, remain subject to d]]> Sun, 18 May 2008 17:50:05 +0000 add http://nitpicker.pbwiki.com/JustGo email.hidden@example.com (Nat Fast) Nat Fast edited JustGo Content Addition - TBD
Content Editing - TBD
Zoomed Interface Interface - Single document, multiple resolutions
The basic interface has three elements: a master background, document thumbnail and the arrow cursor.
Master Background is the highest level of the application. It is a static layer that provides positional cues to content management, allowing a zoom back for any document which is in focus.
Arrow Cursor is a users reference within the view and it's movement and placement initiate document behaviors. At times, the cursor is fixed and the document moves around relative to the center of the screen. At other times the cursor moves in a normal mouse interface fashion. These changes are dependent upon the relationship between the screen and the document resolution.
When we first transit the border of the document thumbnail the related document zooms to the extent of the screen. In the above example it zooms to the height extent, keeping the rest of the document pro]]> Sun, 18 May 2008 12:38:08 +0000 mod http://nitpicker.pbwiki.com/JustGo email.hidden@example.com (Nat Fast) Nat Fast edited JustGo Jef Raskin, in his seminal "The Humane Interface" described a hospital information system which used a mouse with the two main buttons dedicated to ZOOM IN and ZOOM OUT. With the screen filled with a lot of information. To fit it on the screen some of it had to be written smaller, or even much, much smaller. To see the stuff written smaller, you go there and zoom in. What was really remarkable, in my mind, was that absolute novices were comfortable and competent with the system in less than a single minute of training. Even computer experts learned the system in less than two minutes.
Since that sounds wonderful, why change it? The zoom buttons are velocity based devices, like joysticks, as opposed to displacement based devices like computer mice. Thus you must pay close attention and stop pressing the button at just the right time so that the text there is the right size to read easily. How could that be improved? Make the zooming automatic and keyed to the size of the text in that location. Put]]> Sun, 18 May 2008 12:34:51 +0000 mod http://nitpicker.pbwiki.com/f/Expanded+Page4.gif email.hidden@example.com (Nat Fast) Nat Fast uploaded Expanded Page4.gif]]> Sun, 18 May 2008 11:52:09 +0000 upl http://nitpicker.pbwiki.com/f/Expanded+Page3.gif email.hidden@example.com (Nat Fast) Nat Fast uploaded Expanded Page3.gif]]> Sun, 18 May 2008 11:52:07 +0000 upl http://nitpicker.pbwiki.com/f/Expanded+Page2.gif email.hidden@example.com (Nat Fast) Nat Fast uploaded Expanded Page2.gif]]> Sun, 18 May 2008 11:52:06 +0000 upl http://nitpicker.pbwiki.com/f/Expanded+Page1.gif email.hidden@example.com (Nat Fast) Nat Fast uploaded Expanded Page1.gif]]> Sun, 18 May 2008 11:52:04 +0000 upl http://nitpicker.pbwiki.com/Getting+Things+Done email.hidden@example.com (Richard Karpinski) Richard Karpinski edited Getting Things Done Fine Google talk, overview: http://v.mercola.com/blogs/public_blog/My-Favorite-Productivity-Expert-Speaks-at-Google-47215.aspx
rediscovered papers: papers: http://www.todoorelse.com/2006/08/page/2/
GTD Connect:
Free zipped packet of articles:
]]> Thu, 08 May 2008 13:51:08 +0000 mod http://nitpicker.pbwiki.com/Getting+Things+Done email.hidden@example.com (Richard Karpinski) Richard Karpinski added Getting Things Done Fine Google talk, overview: http://v.mercola.com/blogs/public_blog/My-Favorite-Productivity-Expert-Speaks-at-Google-47215.aspx
Old rediscovered papers:
GTD Connect:
Free zipped packet of articles:
Get the book at Amazon, the library, on disc
]]> Thu, 08 May 2008 13:47:37 +0000 add http://nitpicker.pbwiki.com/The+Humane+Interface email.hidden@example.com (Richard Karpinski) Richard Karpinski edited The Humane Interface]]> Tue, 06 May 2008 13:12:19 +0000 mod http://nitpicker.pbwiki.com/Health+care+reform email.hidden@example.com (Richard Karpinski) Richard Karpinski edited Health care reform I claim outcome data will work better than info and rewards from pharma detailers does at promoting successful health care.
Other discussions of George Halvorson's "Health Care Reform Now!": http://www.worldhealthcareblog.org/2008/04/21/reverse-engineering-and-the-golden-goose/
In response to "Systematic Reform of U.S. Health Care – One Man’s Meat" in medinnovationblog.blogspot.com on December 30, 2007 I said:
You and your commentors seem to place the concerns of doctor freedom above those of better patient outcomes. You seem to claim that we make faster progress without any system for teamwork among specialists serving a single patient than we would with a shared electronic medical record and a focus on outcomes. If that were so, wouldn't we expect to see outcomes in the USA leading those of the other industrialized nations with their national health services? We don't. Instead, we see much worse outcomes at much higher prices. I agree that if the AMA and other organiz]]> Fri, 02 May 2008 14:40:27 +0000 mod http://nitpicker.pbwiki.com/Health+care+reform email.hidden@example.com (Richard Karpinski) Richard Karpinski added Health care reform I read Halvorson\'s book and came to some conclusions as well

Main news, follow the BIG money to find the BIG savings:
1. Chronic diseases: teach the patients to care for themselves and provide ever more incentives for them to do so until the incentives don\'t pay for themselves.
2. Fund basic and applied research for cures with a twentieth or more of the costs currently incurred; don\'t leave that to big pharma whose incentives are not to cure but to sell drugs.
3. Coordination: require electronic medical record use to get paid.
4. Guidelines: require to record outcomes to support evidence based decision making for both providers and consumers.
5. Provide for inexpensive testing and rapid deployment of successful proposed improvements from every source.
6. Record patient practices in diet, supplements, exercise, and even meditation to correlate with outcome data.
7. My favorite: make the whole process transparent to consumers, providers, and payers.

I claim outcome data will work better than i]]> Fri, 02 May 2008 13:55:04 +0000 add http://nitpicker.pbwiki.com/Change+Congress email.hidden@example.com (Richard Karpinski) Richard Karpinski added Change Congress Be sure to watch Lessig\'s introduction to the plan to Change Congress in the video embedded in his blog at http://change-congress.org/blog/

His talks are on a par with the talks at TED.com and thus in the top tier of what you can find on the web today. It is simply amazing how clear and compelling this Stanford University Law School professor makes his talks. He is a master and a delight and what he talks about really, truly matters to all of us.
]]> Sat, 26 Apr 2008 23:47:59 +0000 add http://nitpicker.pbwiki.com/FrontPage email.hidden@example.com (Richard Karpinski) Richard Karpinski edited FrontPage PBwikiBugs - Problems using this wiki farm
My own health - Current status, discussions, and health history
Change Congress - Larry Lessig is out to end corruption in Congress
Open Questions (add yours too)
What if a list like this one or the one above gets too long?
]]> Sat, 26 Apr 2008 23:39:28 +0000 mod http://nitpicker.pbwiki.com/SideBar email.hidden@example.com (Richard Karpinski) Richard Karpinski edited SideBar PBwikiBugs - Problems using this wiki farm
[http://pbwiki.com/content/business-whitepapers]
.
]]> Sun, 20 Apr 2008 18:52:24 +0000 mod http://nitpicker.pbwiki.com/SideBar email.hidden@example.com (Richard Karpinski) Richard Karpinski edited SideBar PBwiki - the host
PBwikiBugs - Problems using this wiki farm
[http://pbwiki.com/content/business-whitepapers]
]]> Sun, 20 Apr 2008 18:51:21 +0000 mod http://nitpicker.pbwiki.com/Lovable+computers email.hidden@example.com (Richard Karpinski) Richard Karpinski edited Lovable computers YouMost folks act as though our computers worked pretty well. They don't. I'm with Jef Raskin on this point. He notes that you would have difficulty driving if the brake and the gas pedal switched their effects even at predictable times. But computers do that to us all the time. We blame ourselves for using the wrong command gesture for the current application. It's called a mode error.
Raskin started the Macintosh project at Apple, and then later he spent a decade studying how people work, by reading cognitive psychology and such. Then he wrote "The Humane Interface" which explains in detail how to make lovable interfaces which don't lead one into error and don't frustrate users at every turn. He summarized the principles and the rules given in the book in a letter which I have posted at Nitpicker.PBwiki.com/The+Humane+Interface for your pleasure.
When you analyze the situation carefully, we actually need to package the software we use in a very different way.]]> Sun, 20 Apr 2008 13:36:11 +0000 mod http://nitpicker.pbwiki.com/Lovable+computers email.hidden@example.com (Richard Karpinski) Richard Karpinski added Lovable computers
You folks act as though computers worked pretty well. They don\'t. I\'m with Jef Raskin on this point. He notes that you would have difficulty driving if the brake and the gas pedal switched their effects even at predictable times. But computers do that to us all the time. We blame ourselves for using the wrong command gesture for the current application. It\'s called a mode error.

Raskin started the Macintosh project at Apple, and then later he spent a decade studying how people work, by reading cognitive psychology and such. Then he wrote \"The Humane Interface\" which explains in detail how to make lovable interfaces which don\'t lead one into error and don\'t frustrate users at every turn. He summarized the principles and the rules given in the book in a letter which I have posted at Nitpicker.PBwiki.com/The+Humane+Interface for your pleasure.

When you analyze the situation carefully, we actually need to package the software we use in a very different way. When we eventually accomplish that well, ]]> Sun, 20 Apr 2008 13:35:07 +0000 add