Dear Wiki user, You have subscribed to a wiki page or wiki category on "Lucy Wiki" for change notification.
The "BrainLog" page has been changed by MarvinHumphrey. The comment on this change is: Soften the language of some recommendations. Fix a typo.. http://wiki.apache.org/lucy/BrainLog?action=diff&rev1=1&rev2=2 -------------------------------------------------- Innocence is precious: once you have become familiar with a source, any brainlog you might contribute no longer reflects the experience of those who are coming to the material for the first time. Therefore, if you are going to record a brainlog, you should do so right away. == Editing brainlogs == - It you make a "mistake" during testing, it may be tempting to edit the brainlog after the fact to conceal or minimize it. Don't! + It you make a "mistake" during testing, it may be tempting to edit the brainlog after the fact to conceal or minimize it. Please don't! If multiple test subjects make the same "mistake", that indicates that there is a flaw in the design that needs to be corrected. In fact, that sort of pattern is ''exactly'' what UI testing is designed to reveal. - On the other hand, it's probably not a good idea to publish a brainlog that contains egregiously inflammatory material, even if it's an accurate record of your thoughts. Befor you hit "send" -- especially for the first brainlog you write -- step away for a few hours or a day, and consider whether you might want to swap out certain passages for placeholders like "[intemperate rant about XXXXXX here]". + On the other hand, it's probably not a good idea to publish a brainlog that contains egregiously inflammatory material, even if it's an accurate record of your thoughts. Before you hit "send" -- especially for the first brainlog you write -- step away for a few hours or a day, and consider whether you might want to swap out certain passages for placeholders like "[intemperate rant about XXXXXX here]". == Evaluating brainlogs == When evaluating a brainlog, there are two things to bear in mind. - First, blaming the user is poor form. The brainlogger is performing a valuable service precisely by revealing where they went wrong or right, and they are doing a job that you ''cannot'' do by yourself. Instead of criticizing the path they took, consider how you might modify your source material so that the next user doesn't make the same "mistake" -- even if you think it was a "dumb mistake". + First, it's important to avoid blaming the user for "mistakes" documented by the brainlog. The brainlogger is performing a valuable service precisely by revealing where they went wrong or right, and they are doing a job that you ''cannot'' do by yourself. Instead of criticizing the path they took, consider how you might modify your source material so that the next user doesn't make the same "mistake" -- even if you think it was a "dumb" mistake. Second, brainlogs are raw materials by nature, rather than carefully prepared constructive criticism. A critique is a contribution, even if it is impolitic. If you feel miffed after reading a brainlog, consider it a challenge to rise above and extract every last drop of value from it.
