That will depend on how you structure your deployments, on some large tech companies, while thousands of changes little are made every hour, and deployments are mande in n-day cycles. A cut-off point in time is made where the first 'green' commit after that is picked for the current deployment, and if that fails in an unexpected way you just deploy the last binary back, fix (and test) whatever broke and either try again or just abandon the release if the next cut is already close-by.
Isn't the scheme simply agreeing in a shared key and both using it? I'll know that the message is from you if it's signed with that key and is not from me and vice versa, but neither of us can prove who created the message.
True, although using adb requires the use of the usb port, which for some of my projects is highly impractical.
Also, with this move, Google has made it very clear that they don't want people to have any real control over their machines -- so I'm not inclined to think that using adb to work around the problem will always be possible.
It's fine, though. My hobby projects will continue into the future, just probably without using Android.
I know that this is how shizuku (0) does it and it is required anyway if you want to install multi apk applications so stiff won't change for most people then?
Or just keep the car fan running and use the existing AC system (in ventilation mode, no compressor) to keep the car just as hot as outside (instead of much hotter). If you have some spare power maybe even run the AC when the key gets back in range.
Depends on your definition of "right" and "work". It could be a big ball of mud that always returns exactly the required response (so it 'works'), but be hellish hard change and very picky about dependencies and environment (so it's not 'right').
I always heard the "Make it Right" as "Make it Beautiful", where Right and Beautiful would mean "non-hacky, easily maintainable, easily extendable, well tested, and well documented"
reply