A post on Promotion Driven Development yesterday touched on something I really dislike; Rigid Career Levelling. "Level Worthy" is a phrase I feel a lot of managers misuse as a means of pressuring engineers to take on projects. alsutton.blog/post/what-is-lev

A few folk pinged me overnight my time (UK) to say "adb backup" addresses only one exfil vector. That's true, but it's a vector I have the most context on. If I wanted to make all exfil harder my temptation would be to require a factory reset when enabling developer mode.

This would follow the model of unlocking the bootloader; If you enable something which reduces the security of the device you have to wipe the users data, but would be a *huge* behaviour change.

Something pointed out to me on T*itter; Apps targeting Android 12, which aren’t declared as debuggable in their manifest, will not have their app data included in an ‘adb backup’ backup.


I've submitted a patch to the to take the next step in what was probably, externally, my least popular contribution to while I was at Google. Here's the reason I think it's time to go beyond deprecating `adb backup` and remove it entirely. alsutton.blog/post/adb-backup-

Selling things like Single Sign On for big identity providers (e.g. Google) as an additional extra comes across, to me, as pretty sleazy given the maintenance overhead should be lower than maintaining your own authentication solution. atlassian.com/software/access

Al Sutton boosted

Looks like I might be spending some of tomorrow cleaning up some code to push to a public repo so that folk can start building Automotive OS 11 for the @samsung and test apps in their cars…


The original server operated by the Mastodon gGmbH non-profit