I do not feel the same way. This looks easy to use and useful. I don’t think every problem needs to be a ‘deep problem’. There’s so many practical steps to get to
> People want to log in to an account, tell the thing to do something, and the system figures out the rest.
At a glance, this seems to be a practical approach to building up a personalized prompting stack based on the things I commonly do.
Perspective: Former college robotics team member a while ago (2022) (IEEE SoutheastCon)
I definitely see niches for both. Even if you've got some experience an Arduino uno or mega is just an atMEGA with good software support and IO headers.
We'd usually use an RPI and Arduino - connect our 'out of the box' modules to the pi, pi to arduino via uart serial, and wire arduino to the meat and potatoes. The RPI's IO was generally not as good in terms of latency but also if the wrong wire gets crossed suddenly we'd have a dead Pi but the Arduino would shrug it off.
In terms of what model I use it’s going to be latest and greatest out of whatever my org gives me enterprise access to.
I’d probably try the factory ‘droid’ first, but if it fails to solve a problem and swapping to another one means it solves it, I’ll probably never use the factory one again.
I’d consider this pretty normal as we’re moving closer to ‘this is actually a mature stack that devs use for work’. Very few people in my company actually take interest in their development tooling and use whatever came pre-configured. (our stack is not sexy)
(Let me know if I’m incorrectly conflating the ‘droid’ concept with foundation models)
> People want to log in to an account, tell the thing to do something, and the system figures out the rest.
At a glance, this seems to be a practical approach to building up a personalized prompting stack based on the things I commonly do.
I’m excited about it.