my interest in this would be to customize the cleaning plan/logic... especially regarding traversing difficult carpets edges (which my roborock struggles with)
maybe something like:
- this specific part of the carpet is the best place to enter onto it
- once successfully on a carpet, stay on it until done cleaning it
if you have all of that info, could you then automate the mix transitions by sending MIDI commands back in? would be fun to play a playlist or radio but where the track transitions are automated, phrase-matched and non-trivial (perhaps lasting for a number of phrases)
That was my experience too. The experience with powerline ethernet adapters was unbearable on a daily basis.
We had an unused coax (which we disconnected from the outside world) and used MoCA adapters (actiontek) and it's been consistently great/stable. No issues ever... for years.
> moving toward a world where coding isn't really about sitting down and grinding out syntax
Love the idea of "coding" while walking/running outside. For me those outside activities help me clear my mind and think about tough problems or higher level stuff. The thought of directing agents to help persist and refine fleeting thoughts/ideas/insights, flesh out design/code, etc is intriguing
I really like the nest encoder/button feel, so I was considering trying to hack mine into a becoming desktop volume control/button... but probably lacking the skills to not make a mess of it. Would love to see how you interface with the existing hardware!
didn't read article due to paywall, but the answer is most likely yes. i was able to build a basic 2-degrees-of-freedom robot-arm grabber using lego technic and power functions and was controlled by scratch on a raspberry pi. lego also has pneumatics.
Did same but for Asteroids. Had a working wireframe version after only a couple of prompts! I think using the term "Asteroids" in my original prompt was a bit of cheat/shortcut.
My lessons learned for prompting were to have project broken down into clearly defined modules (duh...), and to constantly feed the latest module source back in as context along with the prompts. This helps ground the responses to only adjust the code related to the prompt, and to not break stuff that was already working.
Should we be checking in our prompt history into version control as a kind of source code or requirements spec? Seems prompt revision and improvement would be valuable to keep a history of.
In the rare event that robovacs manage to traverse the treacherous rug tassels, their algorithm should cause them to stay on that rug and finish it before exiting.
maybe something like: