and all it took was two decades and millions of spend in anti-EV lobbying before they finally gave in, huh
(also kind of wild to me that an EV focused blog wouldn't mention this a single time since Toyota is (was?) arguably one of the staunchest and most stubborn anti-EV manufacturers out there)
except this establishes case law and creates a template for other states to pursue similar cases (which looks like it would include actual reports to labor agencies for monitoring)
> The settlement goes beyond compensating for past violations. Going forward, as part of the settlement, DoorDash must submit detailed data reports to DCWP every month for three years, which the agency will use to monitor the company’s compliance with the law and the terms of the settlement.
you can also develop pro-social coping mechanisms like open-mindedly talking to someone who opposes you and trying to understand their worldview because you trust that it might expand your own
but, yeah, I doubt pro-social traits are common at the top of any hyperstrict hierarchical organization like the USAF
see what we need is another technocratic priest class that unaccountably decides who deserves access to salvation based on how much cash is paid out and how powerful the patrons are
because the tooling is struggling to catch up and adapt. there's still no vetted all-in-one solution that does code review, charts quality metrics, ingests incidents, and writes tests. there could be but each solution would necessarily need to be so bespoke to a codebase that you might as well hire some AI-pilled QAs and come up with it yourself (which is my current job, more or less)
smarter companies are coming up with internal tools that dogfoods on itself which means vendors can't match specificity. but those are the companies where the CTO codes and contributes regularly, and are able to pull the strings across the company to get something like that running
I compare that to the last place I worked where the CTO hadn't coded in decades and was throwing spaghetti at the wall trying to figure out how to use AI. this meant we had designers/PMs shipping directly to prod and but for the sake of a very stressed out Staff Eng and I, they would've force pushed everything with zero testing. but even still, there were TPMs building out a central TPM dashboard to help with cross-team collaboration. and that was largely because their director was very good about getting all of TPM to buy-in, set up their specific configs, and adopt consistent roadmap templates
it all depends on if your leaders actually know what to do with AI or if they listen to some dumbass podcast by a barely-know-anything influencer to drive how they approach things and are looking for hail mary throws
don't worry, we're prolonging retiring coal plants and building a lot more gas turbines to meet (and really exceed) capacity needs on a state-by-state basis and just completely abandoning the Paris Agreement and any clean energy goals
They don't specify if they were public or private keys though.
And even if private, whether they're not just generated per-user anyway, to grant muse the ability to do key-based auth on remote servers (and obviously leaking 'your' own keys wouldn't matter to meta)
I was hoping for a little more detail in that regard, that's the only potentially large finding. I truly can't imagine meta left production ssh keys in the agent VM, it just wouldn't make any sense though
The entire point of Muse is that it's an agent with superuser access to a Linux VM. Of course this can include public and private keys, but these are in a way all your keys as the user of the agent.
(also kind of wild to me that an EV focused blog wouldn't mention this a single time since Toyota is (was?) arguably one of the staunchest and most stubborn anti-EV manufacturers out there)
reply