Bookmarklets are a great way to add functionality without writing a full-blown browser extension.  They should work in all the major browsers (even Opera which I love).

I have created simple bookmarklets to adjust screensize.  It works when only one tab is open, but I can check the responsiveness of my design quickly.

Open source development works when,

1. Capital goods required to do the work are cheap.
2. The limiting factor on the work is human creativity and attention.
3. The work is intrinsically rewarding.
4. There is an objective metric for success that everybody in the hive mind can agree on without too much effort. Without that condition you get thrashing.
5. Zero-cost communications.

Any designer knows Item 4 is a problem: different types of users with a wide range of experience, conflicting goals, etc.  The open source community is starting to recognize that UI design requires a single vision. They are appointing “UI dictators” within each project who “get their way.” “It’s better to have a flawed individual vision than try to do it by committee.”

EconTalk: Eric Raymond on Hacking, Open Source, and the Cathedral and the Bazaar
(program notes and audio)

I am making my presentation available here as a download.

This link is a PDF file, but if you want the original, please just let me know and I will get a copy to you.

Using Personas with XP at LANDesk Software, An Avocent Company

He mentions that every innovator’s tool kit includes these three things:

1. Questions
2. Experiments
3. Self-Reliance

Key points include:

• Borrowing ideas from the Past – look at ways others have solved the solution before you then try variations on them
• Ask a lot of questions
  • Why is it done this way?
  • Who started it and why?
  • What alternatives did they consider?
  • What are my or my friend’s biggest complaints about how it is now?
  • How has this been done in other locals, cultures, or throughout history?
  • What assumptions were made or constraints did they have?
  • How can I apply any of the above to what I do?
• Try things yourself
  • There is no substitute for first hand experience when trying things
  • Don’t be afraid of risk – the bigger the innovation, the greater the risk
• Try, Learn, and Try again
  • This could be called iterating your design
  • Remember what Edison is attributed for saying "I haven’t failed, I have found 10,000 ways that don’t work"

(Warning: PDF Link) The Changing Face of Programming – Brian Kernighan

(Warning: MP3 download) The Changing Face of Programming – Brian Kernighan

At the end he references Fred Brooks and his 1986 article “No Silver Bullet”

No Silver Bullet

Kernighan quotes:

“There is no single development, in either technology or management technique, which by itself promises even one order-of-magnitude improvement within a decade in productivity, in reliability, in simplicity.”

Brooks also states that he believes the hardest part of developing software is always going to be the design/conceptualizing stage.  He says:

I believe the hard part of building software to be the specification, design, and testing of this conceptual construct, not the labor of representing it and testing the fidelity of the representation. We still make syntax errors, to be sure; but they are fuzz compared with the conceptual errors in most systems.

If this is true, building software will always be hard. There is inherently no silver bullet.

Techniques and tools are discussed at introspectiveH.

We think it’s worth examining.

The UIE Podcast

Example at Keith Robinson’s blog

Full interview (30 minutes)

• Reading light text on a dark background
• Line length and readability
• Screen font for captioning and subtitles
• Text Readability and Contrast