"But with a groupware product, nobody would ever work on it unless they were getting paid to, because it's just fundamentally not interesting to individuals."
But: I'd count a wiki as groupware, and 'have a place to plan my Burning Man camp with my friends' definitely meets his criteria for useful software (cough).
But: I'd count a wiki as groupware, and 'have a place to plan my Burning Man camp with my friends' definitely meets his criteria for useful software (cough).
Mostly basic principles of survey design, so applicable beyond software. Plenty of useful nuts and bolts stuff.
Would be nice if people stopped considering the success of open source (both as a development model and in terms of corporate adoption) as this impenetrable mystery.
This whole "less is more" thing can go too far. All else being equal, more features = more customers. Yeah, even for the iPod. The iPod's design would have gotten it nowhere if it didn't have the key features.
Too. Many. People. (see also)
(the post that started all this should be required reading in every application design course, although I think his reductio gets a little absurdum ... wait a minute, does application design exist as a discipline at all? programming, database design, UI design, sure ... but application design understood as a very special case of product design?)
(what the apple process looked like)
(the post that started all this should be required reading in every application design course, although I think his reductio gets a little absurdum ... wait a minute, does application design exist as a discipline at all? programming, database design, UI design, sure ... but application design understood as a very special case of product design?)
(what the apple process looked like)
The benefits of mixed determinism and non-determinism in parallel programming.
Perl: making the hard things easy, and nested data structures fucking impossible.
application design methodologies
Looking for lightweight processes for going from "an app that does X", through mock-ups and use cases, all the way to a functional spec. Links below may or may not be on target.
- IBM: user-centered design
- Apple Human Interface Guidelines: The Design Process
- Joel on Software: Painless Functional Specifications (with useful example spec)
- And finally, putting to rest the idea that any of these will work the first time: c2 wiki: Iterative Development
Yahoo! Libraries for Web Development
UI Code Library -AJAX-yjavascript
Design Pattern Library - including links to where a pattern is used by Yahoo
(some people seem to think that prototype [documentation] and dojo are better)
see also: Ajax Patterns
UI Code Library -AJAX-yjavascript
Design Pattern Library - including links to where a pattern is used by Yahoo
(some people seem to think that prototype [documentation] and dojo are better)
see also: Ajax Patterns
