I just tried /goal for a big refactor job with GPT 5.5.
Oh wow, it just keeps going until either its done or I run out of tokens.
8 hours of slow, deliberate refactoring.
I quite like it!
Want your robotics field PC to share data with the world but don't want it to be exposed on the internet?
Use a cloud service like AWS or cloudflare and have it upload data to a public bucket, then build a simple web page that renders that data.
Simple architecture, easy to do and its usually free if you keep your data small and your web hosting to be a simple static page.
btop is my favorite terminal interface at the moment.
It shows me system processes, CPU load, GPU load, hard drive space, networking.
And it looks so cool doing it!
sudo apt install btop
@GreeneElizabeth Whatever get the job done the fastest, but I’m still a fan of Ros, at least I get an architecture I know has worked for tones of other robots. And should scale as my robot complexity grows
When building your Minimum Viable Robot, use as much off the shelf as you can.
It's super tempting to want to write or generate all the code from scratch, to build your own electronics and circuit boards.
You'll tell yourself that you are building IP, but actually you are just wasting time.
Your minimum viable robot just needs to prove the problem can be solved and someone will pay you.
Everything else is premature optimisation.
If you can't have hard conversations it will happily draft a diplomatic non answer so no-one on your team knows whats actually been decided.
And it will keep telling you how awesome you are as you do it.
So be careful.
AI will amplify your worst traits if you let it.
If you're a lazy developer it will happily cut corners for you until nothing works.
If you are a micro-manager it will happily design a scheme to encourage every employee to quit.
Yet in the age of AI I wonder if anyone has turned their agent to the firmware on this thing and gotten useful stuff out of it?
Have you tried fixing your old Lytro Illum?
Has anyone done any hacking on the Lytro Illum SLR camera?
It seems roughly once a year I get the Lytro camera out and see if it's useful. This time it's because I currently have a tough computer vision problem and I wondered if this light field camera could help.
But sadly the firmware is locked down, and all the repos are for the earlier model. It seems that Lytro just made a cool piece of hardware and then disappeared, leaving all these units lost and unsupported.
@ooeygui This is a good idea. I usually don't use MCP servers as I like to just ask the chatbot to run the commands, but I can see myself booting this up next time I run into something problematic
When Error Messages Hide the Real Problem: A ROS 2 Lesson
Opaque error messages are a special kind of frustrating. They tell you something is wrong, but not what or why.
I hit one recently that perfectly illustrates this.
Why put shoes on J the robot?
His feet are perfectly good, and made of grippy rubber. But man, I don't want to have to figure out how to replace a worn out foot when we could just switch shoes.
Thankfully he's a humanoid, so there are plenty of shoes for him!
If you hit "sequence size exceeds remaining buffer" when mixing ROS 2 versions, now you know: check your distro compatibility first. You'll save yourself hours of debugging.
The real lesson:
ROS 2 distros are only guaranteed to work with their own version. Humble with Humble. Jazzy with Jazzy. This is reasonable—it's how versioned systems work.
But the error message doesn't tell you that's the problem.