Thanks for your feedback.
We receive requests for help at every level.
There are many simple, basic, requests for "how can I create a macro that does X?", where "X" might be "resize and move a window", which can be done with one KM Action.
OTOH, there are some requests for help with much more technical workflows.
Some of these are asking for help with specific scripts/languages, so if you don't use or understand that language, it might be intimidating. This is true for me.
When people are asking for help with a detailed, long Bash Shell Script, or Python Script, it might be intimidating to me, but I just don't let it.
I scan the post to see if it is of any interest to me. If not, I just ignore it and move on to the next topic.
That is one reason that I always try to provide a non-scripting solution to requests, if it can be reasonably done without a script. For myself, I might write a script, but for pubic posts I present the non-script solution.
However, one thing we all have to recognize is the KM is designed so that you can combine its many Actions in lots of ways. This comes down to visual programming.
But this design is one of the things that makes KM so powerful.
Many (most?) of us learn best by seeing examples. So that is why I often provide a Getting Starting list to new users, that includes this: