Elez did in fact have write access, allowing him to push unvetted and untested changes straight to the Treasury's payments system — a nightmare scenario that could introduce all sorts of cybersecurity vulnerabilities and leave doors open for adversary hacker groups
Absolutely every prong of this attack on the government is for one goal: to declare mass emergencies by way of manufactured errors and chaos in order to seize ultimate power.
He wouldn't want to get his young tech bro hands dirty with Fortran. Surely there are cross-compilers that will translate your mission-critical payments Fortran to JS, maybe with an intermediate Rust and/or TS step. Fortran -> TS -> Rust -> JS, or similar, it would be quite a feat to behold. Never mind testing (that would be "wasteful" and "inefficient"), just push to prod and sit back and watch then chaos unfold, then blame it all on Biden and, I dunno, Bill Gates maybe.
He could push directly to main/prod, so there weren't explicitly any code reviews or necessarily oversight. Also, that code would be private. Only an insider with repository access could tell us that.
That said, I also want to know. I'm guessing we'll hear about it soon enough.
Der Müskrat has been screaming “LEMME AT THEM COOKIES” for a month straight while hiring unpaid cookie monsters. Whether or how it already happened, it’s pretty clear the cookie jar is gonna get raided by someone.