#1: good examples and specificity are definitely lacking in much documentation. I've been struggling with what to call it recently, because my company is extremely bad at recalling "oh, what does this feature do?". I think what is needed is documentation of business rules (eg an X can have many Ys, but the Ys cannot overlap if they are of the same type). A simple statement like that, with a simple test case, goes a long ways towards helping to automate QA, allowing developers to document code in a consistent manner, and documenting what is expected to happen for the end user.
#3: figured it was something like that, but was curious. ;-)
#4: I don't have the vocabulary either. Have you stumbled across pandora.com? It is interesting because they do have people who categorize and have the right words, and although the suggestions are not always the best, the "we selected this because the song you picked had X and Y and Z, and this does too" is pretty neat.
Comments 1
#3: figured it was something like that, but was curious. ;-)
#4: I don't have the vocabulary either. Have you stumbled across pandora.com? It is interesting because they do have people who categorize and have the right words, and although the suggestions are not always the best, the "we selected this because the song you picked had X and Y and Z, and this does too" is pretty neat.
Reply
Leave a comment