Depending on your firmware version, most jailbreak guides will have you either create an empty directory with the same name as the OTA firmware file (causing any OTA downloads to fail) or install an extension called `renameotabin` which renames the binaries responsible for performing the update, rendering them inaccessible.
This is roughly how I’ve found myself using jj naturally. I find it hard to “tell the story” of a change ahead of time, because the design often only becomes clear after some exploration. It’s much easier to land at an implementation I’m happy with, then work backwards and shape the commits into the story I wish I’d taken.
Funnily enough, I used to! (I even contributed a few PRs). However with my new home battery I need more granular control to do some tariff arbitrage that EVCC didn't really support. Great project though!
> The industry has a lot of work to do in this department
The “industry” has an answer to this problem. It’s called a blameless post-mortem.
Don’t blindly externalise the blame onto everyone else, assume we work in a imperfect world and build safety around the process such that this doesn’t / can’t happen again.
If all you do is finger point to shift the blame, then you’ll have an infinite number of avoidable incidents to show for it
> Issues like this occurred and still occur without vibe coding
Right and so you focus on fixing the elements of the process you can control.
Gawiser filed a “writ of execution” (another $240 in court fees) just yesterday, which would allow Texas law enforcement to seize and sell off enough of Tesla’s property as would be required to pay the judgment against them.
I use pi (https://pi.dev/) as my coding agent which allowed you to use your subscription until Claude recently introduced extra usage and I was routinely using the equivalent of my Claude Max subscription in an hour multiple times a day.