But there are Android phones that come with bootloader/OS lock, which often means old device is stuck with some ancient OS version (and some bundled bloatware), instead of being able to be reflashed to a recent LineageOS.
- the "vendor's" right to substitute himself for a replacement they subcontract (via employment or otherwise) to, irrespective of the client's deemed suitability of the chosen replacement
- the "vendor's" right to a significant level of autonomy, such as the ability to choose their working hours and lunches, and have high level control over their workflow
- the process of determination 'employee' vs 'vendor' must be significantly documented and can be challenged in retrospect for years after completion of the contract
Falling on the wrong side of a determination could leave the client liable for mandatory national insurance and pay-as-you-earn tax deductions. Now HMRC need not prosecute individual contractors, but instead clients (who may hire hundreds of contractors), making the enforcement process much more efficient for them, and much higher risk for the clients.
Net result for companies: building big overnight temporary teams out of contractors e.g. for 6-12 month projects are vastly less likely to do so, for fear that at some future date, the tax man could claw back a year's worth of tax for e.g. 20 contractors on the same project, with non-compliance and late payment penalties lumped on top (which themselves increase with respect to how long it took HMRC to get around to investigating you). It could be the case (hypothetically) that it would only require one member of a team to report the inability to substitute, or the presence of a line manager, for an entire project team's worth of tax to get a question mark placed next to it.
Net result for contractors: anyone who understands what's going on has either pivoted into becoming a permanent employee, avoiding the whole mess, since contracting is an expensive activity to begin with, and the premium has now been removed, or has banded with a few friends and attempted to set up "micro agencies". I've already encountered these, where substitution was advertised very early in conversation.
Net result for the market: it will be all but gone by April 2020.
There is surprisingly little info available on how to do code signing for Windows now. I don't want to use a physical device - with fully remote teams it's not feasible. Eventually settled on Azure KeyVault with Digicert (I don't like Comodo aka Sectigo). There is really little info available on how to get it all to work together, and you have to spent around $600 before you can even try and see whether it can work.
Now that it's all configured, the setup works well. The new setup of doing the signing via Azure is more secure than storing the private keys on the CI system. But I never thought that signing an app for Windows would be more difficult than signing for macOS or iOS.