Comment by siliconwitch

The way the scripting engine is designed is such that it’s not really a problem to iterate in the field. If your code has an error, simply adjust and restart the script. Sure if you have the device hooked up to motors which could break things then of course you might want to do that in a controlled environment, but for applications like sensing that’s seldom a problem. The benefit you gain here is a very fast iteration cycle where you can easily test against real conditions, rather than in a lab where it might be hard to validate things. No need for heavy firmware testing, rolling out OTA updates, or worrying about bricking devices

In general I agree with you for complex projects, but these are typically where you can afford to have 2-3 engineers spend a year developing a specialised solution. Building infrastructure to safely roll out updates, managing data plans, handling compromised devices. All of this becomes a massive amount of work before you’re actually solving a problem for your business

The target audience isn’t necessarily engineering companies, but rather those that might have a few tech generalists. Their goal simply being to add some kind of sensing that might transform their product or service