I initially started this post as a reply in the “Thoughts on Modes” topic in this forum. Since after 4 days it hasn’t gotten a single direct response, I thought to post it here in its own topic.
First of all, I want to assure you that we here at support are not offering highly technical solutions or telling people to code when they email us or chat in at http://support.smartthings.com. We’re here to help regardless of your technical abilities, and we’d never tell someone that they need to code something if they hadn’t already expressed an advanced technical ability.
I’m maybe immodest but I think this is at least partly a response to me. First off thanks for addressing this. I never meant to suggest that “Just code something” was official policy of Physical Graph. I was instead trying to point out that, at least at this stage of ST’s development, it’s a prevalent attitude.
A natural one, when of course most of the development team are coders. Many of the early adopters are too. Maybe I’m unique here in that I’m very technical, but not at all a coder. Sure, I’ve puttered with Applescript, but when I took a PHP course it went in one ear and out the other, and while I have UNIX command line skills, I wouldn’t dare try to write a shell script for production without another person with actual programming skills looking at it.
No, I was talking about an attitude here in these forums and also as reported to me second hand as being the attitude of the devs. (Damn if I recall where but I’m sure it was here in some topic, not even one I was initially involved in.)
That said, at the moment in ST’s development, to get what seems to be relatively straightforward inputs turned into outputs, coding IS required. Follow this link to see what I mean. I asked a question and was immediately pointed down the Groovy rabbit hole.
I had already started writing down my thoughts about this, and now that we’re into it here, I’m going ahead and publishing it with the warning that I haven’t really polished it and I’m sure there’s more to expand on, but here it is.
And I’m going to add one more thought to this, more of a challenge really: I challenge all the actual employees of ST who use ST at home (which I hope, at least in the case of coders and UI people is 100%) to go home and remove every bit of custom code from their setups, at least temporarily. I really think it’s important to eat your own dog food, as the saying goes. Only by living without custom code will you understand the experience you’re offering to those who can’t or won’t code for their needs.