

Yes, so now when there’s a success, it gets attributed to AI. When there’s an outage, that’s the fault of humans not reviewing correctly. These senior engineers will get fucked in all scenarios.
Also on Mastodon: @[email protected]
Want to send me a tip? XMR:89oiUKyACFZ655sTikh42RF8wpd46EQDmbTQUQiHHRWFEatjp5xxj4tZBhMMfjC4X45qvq4EdEGXkBsdxT1kP9xyVia8mPD


Yes, so now when there’s a success, it gets attributed to AI. When there’s an outage, that’s the fault of humans not reviewing correctly. These senior engineers will get fucked in all scenarios.


Code signing for EXE is already a thing. And @[email protected] is right, the same thing is happening there. Restriction are getting more inconvenient, with Microsoft now talking about a maximum code signing certificates validity of 72 hours, with identity verification getting more strict too. Valid code signing certificates are not mandatory yet but I guess it’s a matter of time before we need to type powershell commands to disable restrictions.
Looks similar to Plume, the “no DB required” is neat though!