The ‘two tribes’ raise their ugly head again. I’m not a programmer—and lack the aptitude. I don’t buy the “oh it’s technical, I _can’t understand” mantra I’ve detected above. Othering that thing—or those people—who have different skills is not helpful.
I came to understand Tinderbox not because I cleave to the Arts or the Sciences (as if these are innate binary human conditions), but because I wanted to solve a problem where other tools had failed me. If you are from an arts background and learn how to write an action, you are not diminished as a human.
I also don’t buy the self-regarding “I’m smart so if i can’t understand the app it must be dumb and badly made”. That’s just an unwillingness to accept we find some things hard, or unfathomable. My experience, when struggling is to ask for help and try and explain how and where I’m lost. Just abusing those who would help because they don’t intuit my special needs seems self-serving.
Learning the deeper parts of Tinderbox isn’t some performative competition. Even if none of it makes sense, you can always ask for help—but do remember not to sneer at people who understand something you cant’t or worn’t understand. Not least they give their time and effort, for free to help problems that only you may have. Does such assistance deserve sneers about ‘technical’ expertise.
It’s hard to help people who forgotten how to treat others as fellow humans and just demand and give nothing in return.
The Tinderbox community is a broad church. We have lots of people from all sorts of walks of life, be they ‘technical’ or not. So, as your forum moderator, can I ask us all (so as to single out no one person) to be a bit kinder and more generous.
Over the 16 years I’ve assisted this community, the most compelling stories are those who fought through their prejudices and false assumptions about how things must be (be they ‘technical’ or ‘non-technical’, whatever that means) and asked for help and acted on it.
There are improvements that can be made to the range and type of learning material available, but a lot of what I see are pre-emptive barriers: "I won’t use assistance unless it meets my following conditions (which invariably then aren’t explained). I both write and use documentation, the best interactions are people who don’t just say “it’s all rubbish” sort “it’s not written for me” and flounce off. Better are those who say where they get stuck and what concepts are blank to them. Tellingly, the’ve made an attempt to understand, and their comments yield real insights which I certainly put to use in what I write and make.
So, instead of asking for “easy” or useful" or “pertinent” which are all subjective, please surface where you get stuck. If you’re not sure why, explain what you imagine (intuit) will happen, and be open enough to understand so thinks may work in ways you personally don’t understand.
I’ve accepted that I’ll never be a programmer. As non-programmers, Tinderbox’s internal scripting may seem like ‘coding’, but that’s unfair programmers; the latter is more complex and nuanced. If we set aside our pre-emptive rejection of what we disparage as ‘code’ it leaves us more open to leaning. If I can learn it, I’m unconvinced others can’t if they would only stop convincing themselves they can’t.
TD;DR You can if you try, and are not embarrassed to ask for help.