Louisville, KY
Greg is a retired neurologist in Louisville, Kentucky, with a long-standing interest in computers and programming, beginning with Fortran IV in the 1960s. When Linux and open source software came along, it kindled a commitment to learning more, and eventually contributing. He is a member of the Scribus Team.
Authored Comments
I think it's important if not essential to have good communications between developers and those writing documentation. For one thing, this is the best way for documenters to keep up with new features, or perhaps old features that now work in a different way. In addition, the documenters can give feedback about something that doesn't work as designed, or could work more efficiently with a little change in code. So it's a two-way street.
There is a saying that was used when I was in medical training, about how to learn some procedure you've never done before: "See one, do one, teach one."
The idea was to very briefly explain how to rapidly come to a deep understanding of a procedure or task that's new to you. Even if explained in detail, you don't really know how to do something until you actually do it yourself, and finally, the depth of your understanding must be even greater to be able to explain it to someone else.