Hi all,
Just a tiny story: I have almost completed a new plugin and as usual,
I finish by writing the docs (in english and french...)
As always, the fact of writing the docs (i.e. explaining how it works
or should work :-) brings changes in ergonomics, highlights some
points badly designed and often makes me aware of some possible bugs.
Conclusion: taking care over the docs is a very efficient way to get
a good product.
As you write the docs, you have constantly a third party in front of
you: the end user :-)
And he is demanding...
Le 21 juin 05 à 20:45, jbv a écrit :
if by that you mean that the action of explaining step by step
what you are trying to do to someone else (even someone who
doesn't understand a word) often helps finding the origin of the
problem and/or a solution, I must say that it's a well known fact
in psychology : putting a problem into words for a third party is
a very efficient way to solve it (or at least get closer to the
solution)
and I've been practicing it for years (and not only in coding).
Best Regards from Paris,
Eric Chatonet.
----------------------------------------------------------------
So Smart Software
For institutions, companies and associations
Built-to-order applications: management, multimedia, internet, etc.
Windows, Mac OS and Linux... With the French touch
Free plugins and tutorials on my website
----------------------------------------------------------------
Web site http://www.sosmartsoftware.com/
Email [EMAIL PROTECTED]/
Phone 33 (0)1 43 31 77 62
Mobile 33 (0)6 20 74 50 86
----------------------------------------------------------------
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
