I’m a software designer currently living in Salt Lake City, Utah. I like to make nice apps and websites.
Sometimes I share things of interest here. Subscribe to the RSS feed with my open source
reader.
Surprisingly, developers and designers feel like an underrepresented segment of "Pro" users even though we build and design all of the iOS and mac software. I always wonder if the in-house design and development teams at Apple have the same qualms and complaints that makers of 3rd party software have.
So we are coming full circle. Overuse of JavaScript. Using JavaScript to build static, undynamic, barely-interactive websites. Supporting only certain browsers for no technical reason. Best viewed in Chrome.
What's most interesting to me about this, is the question as to whether there will be more team coordinated pacing efforts. Will strategies similar to road bike racing begin to appear in marathons?
When a computer and its users interact at a pace that ensures that neither has to wait on the other, productivity soars, the cost of the work done on the computer tumbles, employees get more satisfaction from their work, and its quality tends to improve. Few online computer systems are this well balanced; few executives are aware that such a balance is economically and technically feasible.
I've heard this called the Doherty Threshold or Doherty Response Time. It may seem out-of-date, but I think it's definitely still applicable today when thinking about transitions and how they may delay a user's response.