Wednesday, May 21, 2008

Changing learning curve ... is developer's learning effort

How easy is to change the learning curve for the users of your programs? The answer lays on your response to What is ergonomics?

Example of not to do: to name Arbiter.Choise<>() (is suggesting a decision to make by using a predicate ) instead of Arbiter.TakeFirstArrivingFrom<>() (more clear for the reader) or Arbiter.FirstReceivedFrom() or even Arbiter.Any<>() sounds better.

I polluted my mind with Implementing a Simple 2D Object Tracker. I'm sorry right now, because i want to make my own system of recognition, or at least to take the time to think the best approach. After that to see other programmer's solutions.

No comments: