I was just thinking the same! Spent few hours a month ago measuring 120mm noctua fans to build a custom mounting bracket for a rack cooling module I was making.
Never finished it because I kept having to tweak and remeasure, but now I can definitely go back and finish it!
Most of my friends worked restaurants or bars when I was younger, tips were something some tourists would sometimes do and it would generally go into a pot for throwing a party for the staff few times a year. I have never tipped or seen a local tip in my home country.
Tips weren't a part of my friends income. The restaurant/bar paid them a salary.
Last weekend I was debugging some blocking issue on a microcontroller with embassy-rs, where the whole microcontroller would lock up as soon as I started trying to connect to an MQTT server.
I was having Opus investigate it and I kept building and deploying the firmware for testing.. then I just figured I'd explain how it could do the same and pull the logs.
Off it went, for the next ~15 minutes it would flash the firmware multiple times until it figured out the issue and fixed it.
There was something so interesting about seeing a microcontroller on the desk being flashed by Claude Code, with LEDs blinking indicating failure states. There's something about it not being just code on your laptop that felt so interesting to me.
But I agree, absolutely, red/green test or have a way of validating (linting, testing, whatever it is) and explain the end-to-end loop, then the agent is able to work much faster without being blocked by you multiple times along the way.
Yeah, actions shouldn't be used like this, as per their terms[0]:
> Additionally, Actions should not be used for:
> * cryptomining;
> * using our servers to disrupt, or to gain or to attempt to gain unauthorized access to, any service, device, data, account, or network (other than those authorized by the GitHub Bug Bounty program);
> * the provision of a stand-alone or integrated application or service offering Actions or any elements of Actions for commercial purposes;
> * any activity that places a burden on our servers, where that burden is disproportionate to the benefits provided to users (for example, don't use Actions as a content delivery network or as part of a serverless application, but a low benefit Action could be ok if it’s also low burden); or
> * any other activity unrelated to the production, testing, deployment, or publication of the software project associated with the repository where GitHub Actions are used.
Specifically the next to last point, shouldn't be used "as a part of a serverless application".
Never finished it because I kept having to tweak and remeasure, but now I can definitely go back and finish it!