tatewise wrote: ↑28 Apr 2022 13:37
My knowledge is not that mysterious. I just use a logical detective approach.
I think really "getting your mind around software" is more complex if not mysterious. It's not just knowledge; it's also an approach, an empathy and some degree of skill.
I think we need to understand that there are two broad approaches that users tend to take; those that just learn mechanistically a set of instructions that give the desired effect, and those who are not "afraid" to have a feel around and are willing to take the small risk that they may "break something". In doing the later your discover for yourself what can be done. My late mother was in the former category and relied on numerous laminated cards giving step by step instructions - the idea that you could just "click around" or "try right clicking" was alien. I think this is partly a generational thing and partly whether people feel intimidated by "systems".
When I was introduced to Lotus Symphony (an allied program to Lotus 1-2-3, but with added basic word-processing, graphics and database abilities), I had 2 or 3 days one-to-two training by two instructors who really understood the program and enabled me to get into the "mind-warp" of the person (I suspect it was a single person) who master-minded the program. You also generate an ability to think "that functionality [possibly as simple as switching an option on or off] must be possible", so you then think "how would they have developed that functionality?". That process of getting into software has served me well - although when the program is written by a committee it is more difficult.
Finding your way round software is also a skill - possibly like playing a violin ("that fingering not comfortable, try getting the note on a different string?"). "Customise" not under "Edit" - try "Preferences", try "Preferences" under "View" or "Tools". It is almost more instinctive that plain knowledge.
Of course if the single-mind that created the program was also having to work to some external requirement, say GEDCOM compatibility - or use of a library of functionality (for instance colo
ur selection), your ability to get into the developer's mind-warp is also dependent on how comfortable they were working with the mind-warp of those who developed say GEDCOM or the library!
