Quote:
Originally Posted by taming
I would go a bit further and say that it really helps to be able to "work and play well" with others. It's a collaborative process, but testers don't necessarily know the whys behind all of the decisions that are made--including why something that seems like a big want isn't being addressed at the time of testing.
People bring different skills to the process. I have only a modicum of knowledge about the technical constraints that may be affecting firmware, but I have years of experience writing technical manuals, curriculum, and developing other educational material. That's my strength, I think. So I am not the person who will be having tech discussions with the developer, I'm the tester that says things like "document the differences in this way" or "I want a darker font".
|
But taming thats a real world response. I for one think "I want a darker font" is the most important thing a beta tester can offer. Because rather then the firmware only doing what the developer thinks should be force fed to us, its nice to have input on features we really want. Not just what the developer says we should have no ifs or buts about it!. BTW I am not saying kobo is doing that, its just an observation from other things.
Any way real world input is the most important thing a developer has. It helps them to develop real improvements, not just stabilizations and limitations. Theres nothing worse then a developer crippling their hardware just because they feel no need for things that they dont use.
regards
jack