DeRose: Designing pro creative apps (Part 1-3)
DeRose: Designing pro creative apps (Part 1-3)
Posted Jul 13, 2011 1:04 UTC (Wed) by dlang (guest, #313)In reply to: DeRose: Designing pro creative apps (Part 1-3) by rgmoore
Parent article: DeRose: Designing pro creative apps (Part 1-3)
I'm nowhere near that perfect about labeling all my removable media accurately enough (and I have trouble understanding how you would put enough detail on some of the smaller cards)
the problem isn't with having a way to import everything from the card, the problem is in kicking off a job to do so as soon as the card is detected by the program.
Posted Jul 13, 2011 4:31 UTC (Wed)
by rgmoore (✭ supporter ✭, #75)
[Link] (4 responses)
I don't with the cards from my camera. I know what's on them because they never sit around for long enough for me to forget. When I'm done with a shoot, I download my cards onto the computer and then format them in the camera. They are either full of photos that are recent enough for me to remember taking them or empty. I even have a system to keep my full cards distinct from my empty ones when I'm out photographing so I don't have to check by looking at them in the camera.
I think this is a key part of Mr. DeRose's idea of targeting serious users*. Somebody who takes a few vacation photos or videos the school play may be able to get away with ad hoc organization and workflow. When the files start piling up, that approach gets less and less viable. Serious users are forced to adopt a structured approach to dealing with their data or they'll wind up drowning in it. A program that provides a structure that matches what users are doing is great. One that imagines how they could do things better and provides it can be a godsend.
*He talks about designing software for professionals, but I think this is something of an artificial distinction. Dedicated amateurs like me can be just as serious about our tools as full-time pros.
Posted Jul 13, 2011 10:51 UTC (Wed)
by jubal (subscriber, #67202)
[Link]
Posted Jul 14, 2011 16:28 UTC (Thu)
by sorpigal (guest, #36106)
[Link] (2 responses)
Just because a program is *for* serious users doesn't mean it should raise unnecessary barriers to everyone else, all else being equal.
Posted Jul 16, 2011 15:05 UTC (Sat)
by Wol (subscriber, #4433)
[Link] (1 responses)
Remember the thread on Jack? Where the penny finally dropped that Jack was targeted at a corner case such that while 99 point whatever percent of people didn't need what Jack offered, those that *did* need it made up 99 percent of Jack users?
This is directly aimed at a small subset of "all users". It's aimed at users with unusual needs. If you don't want what it wants, you go elsewhere, you don't suggest that they delete the functionality that 99% of its users want.
I read the article. Seems like many people didn't. It came over quite clearly that the software designers asked themselves "what is a professional workflow? How can we automate it?". The fact that you and me as amateurs think its completely daft merely shows us up as the amateurs we are.
Bit like my brother with emacs :-) When he first used it he dismissed the UI as "totally idiotic". But the more he used it, the more he *understood*, and the more he appreciated how the UI actually was designed to make his life as a programmer easy. Emacs is a professional programming tool. You don't give it to a two-fingered typist.
Cheers,
Posted Jul 27, 2011 17:04 UTC (Wed)
by nix (subscriber, #2304)
[Link]
DeRose: Designing pro creative apps (Part 1-3)
you mean you never insert a card into a machine to see what's on it?
DeRose: Designing pro creative apps (Part 1-3)
He talks about designing software for professionals, but I think this is something of an artificial distinction. Dedicated amateurs like me can be just as serious about our tools as full-time pros.
Dedicated amateurs are usually more serious about their tools, full-time pros are usually more serious about their data and the final product.
DeRose: Designing pro creative apps (Part 1-3)
DeRose: Designing pro creative apps (Part 1-3)
Wol
DeRose: Designing pro creative apps (Part 1-3)
Emacs is a professional programming tool. You don't give it to a two-fingered typist.
A lot of programmers are two-fingered typists, because they taught themselves to type when very young and two fingers works well enough when you have young hands. It's only once the RSI hits that they're forced into proper typing. (Speaking from experience here...)