Posted 30 June 2015 - 07:43 AM
It is awesome when great document/manual creating people join up with great program writing people.
The great programmer needs to be able to get at least the basics out there for the doumenters can make the documentation readable, understandable, even interesting.
I have read some great documentation over the years, but mainly for some simpler programs. The more indepth the program, the more complicated the documentation.
My Jim could decipher it if he was really interested in the program. But sometimes my eyes would glaze over trying to understand some of those instructions. I would be right on the edge of understanding or even have it for a second, but there would be parts that would elude me or confuse me. Thankfully I had Jim to help.
But it shouldn't be that mind numbing to learn a program.
Despite how poorly written, I could still understand it with many programs. But there were times and it seemed that a translator translated words but not the true meaning of those words. They could be taken multiple ways and in conjunction with other poorly translated sections, it would leave me reeling trying to decipher it.
Jim on the other hand, grew up deciphering poorly translated hardware manuals as an electronics technician, and he just had a gift to be able to decipher the hardest manual.
I do not think it should take a genius level brain to understand a manual/documentation. I am considered intelligent - my IQ is considered above average or bright/brilliant level depending on whose chart you use, but I am no genius.
As I say, less intense programs, I can easily decipher on my own, others I needed Jim's genius to decipher at least certain parts for me. He truly had the teacher's gift! He couLd take even the most complex subject and bring it down to true understanding for most people. As I say, it was his teacher's heart.