Hey tech adventurers! 👋
I maintain a little C++ / Arduino library that talks to Teslas over Bluetooth — unlock, climate, charging, the fun stuff. One wrong byte and the car just ignores you. Charming. 🫠
Repo went quiet for a long time. Catching it up by hand? That's weeks of careful suffering. Not because the typing is hard — because you never quite know if you broke something until you're standing next to a real car looking silly.
So I didn't do it by hand.
How I actually work 🐕
Plan first. Get a couple of independent takes so I'm not vibing alone. Make the checks real — automated tests that have to go green — then let an agent grind.
I pointed my Ageent at the library with that shape. Plan the catch-up. Put checks in place. Agent does the busywork. Fail, fix, keep moving. I don't babysit every tiny change.
Same day: what used to feel like weeks became hours.
The Tesla bit is the example 🧾
Before the agent ran wild, I added a small host test suite — known-good messages the car expects, so a change either passes or it doesn't. Short receipts. Just enough so my Agent can fail, fix, and keep going without me re-learning the whole protocol from vibes every time.
Funny part is I finally touched a library I'd been avoiding by refusing to touch it myself. Peak me. 🍕
Top comments (0)