Every time I see a a keyword-based or graphical-based test automation system aimed at allowing "everyone to write test automation" it ends up devolving into thi

Every time I see a a keyword-based or graphical-based test automation system aimed at allowing "everyone to write test automation" it ends up devolving into this. Worse, it gets in the way of the people who -do- end up grasping programming. I'm not in the "it's a talent and you either have it or don't" camp, but I do absolutely believe the core skills of any programming task are in problem breakdown and solution visualization. The best environments serve those two purposes specifically, and preferably as transparently as possible. Environments which end up with a rigid expression in the service of accessibility usually end up counterproductive very quickly because they don't generalize enough. There's a fine line between "opinionated" and "obstinate."