|Problems? Is your data what you think it is?|
Documentation for non-Geeksby skazat (Hermit)
|on Jun 23, 2008 at 03:56 UTC||Need Help??|
skazat has asked for the
wisdom of the Perl Monks concerning the following question:
This is less a technical question and more of cultural question:
My bread-n-butter web app is seeing a lot my attention lately, mostly because a very large hosting company has it as a one-click installation option for it.
This means the barrier to entry to use the program has dropped significantly, but now, when people want to do more with it, the find the barrier exceeds what they know and they feel, not so good.
What words of wisdom should I pass on to these people who want to say, configure a plugin to the program, but configuring a plugin means editing configuration variables on top of script and uncommenting lines. This isn't rocket science, but it's Murphy's Law that if you can mess it up, my Fine Users will.
At least in this release cycle, I can't make this any easier, but I was hoping that, perhaps there's a resource available entitled something like, "Mucking about in a Perl program, if you're not a perl programmer (or a programmer at all!)"
I've personally have been grappling with two types of instructions - one type attempts to go through the steps, as if the person wants to know what they are doing, the other type of instruction just says, "DO THIS" and things will work out. I'm thinking the latter is the way to go, as my Fine Users rather don't care about the former (I'm the one that cares about the former)
Is this something people can empathize, or is it the opinion that if they can't, they won't, and they probably should not. As I said, configuration is uncommenting lines and filling in variables. THis isn't something with a Makefile. Asking my users to make, make test and make install is like asking where the restroom is in the French Provence.
Thanks for any leads.