This is an interesting problem to tackle. It's not clear from the github readme what the output of this looks like, specifically what does it return to the LLM?
> it's not important for a CEO to be good with software engineering
If you are the CEO of a company, you should have expertise in whatever your company does, and If your company is primarily a software company, then you should have expertise in software engineering. You cannot effectively manage something that you don't understand.
> "An AI and a pair of human doctors were each given the same standard electronic health record to read"
This is handicapping the human doctors abilities. There is a lot more information a human doctor can gather even with a brief observation of the patient.
This is the real question. If they are serious about not doing something like this again, they NEED to look at what process failed and let something like this get proposed, designed, implemented and pushed to production. Usually things get reviewed at each stage. Did the people who pushed back on this get steam rolled? If no one pushed back, that's an even serious culture question and the entire org would need training.
A serious "we won't do it again", needs to be accompanied by a COE on this for identifying what went wrong, and identifying what guardrails can be put in place and then actually implementing them.
Owning a decision means you have something at stake if things go wrong. What would happen to Jack if this decision turns out to be wrong? Any consequences?
Are the model weights burned into the silicon / part of the architecture? Or can you update the model weights on these chips?
If they cannot be updated, these chips will be outdated the moment they are made given the breakneck speed at which new and improved models are introduced.
Incredible documentary about the politics around EV's made before Tesla's became mainstream.
People were demanding and protesting asking GM to let time buy their EV'1 after the lease, but they destroyed all the cars. So did Toyota for the EV RAV4's.
Comparing it to X flights maybe correct from a greenhouse emissions standpoint, but extremely misleading from a safety perspective. A jet emits that co2 spread over tens of thousands of miles. The problem here is it all pooled in one location.
Also that statement of 70 meters seem very off, looking at the size of the building. What leads to suffocation is the inability to remove co2 from your body rather than lack of oxygen, and thus can be life threatening even at 4% concentration. It should impact a much much larger area.
what happens if that large enclosure fails and the CO2 freely flows outside?
That enclosure has a huge volume - area the size of several football fields, and at least 15 stories high. The article says it holds 2k tons of co2, which is ~1,000,000 cubic meters in volume.
CO2 is denser than air will pool closer to the ground, and will suffocate anyone in the area.
> Many of the dependencies used names that are known to be “hallucinated” by AI chatbots. Developers frequently query these bots for the names of dependencies they need. LLM developers and researchers have yet to understand the precise cause of hallucinations or how to build models that don’t make mistakes. After discovering hallucinated dependency names, PhantomRaven uses them in the malicious packages downloaded from their site.
I found it very interesting that they used common AI hallucinated package names.
If that was the case, the message should be about a limit on re-enabling the feature n times, not about turning it off.
Also the if they are concerned about processing costs, the default for this should be off, NOT on. The default should for any feature like this that use customers personal data should be OFF for any company that respects their customers privacy.
> You are trying to reach really far out to find a plausible
This behavior tallies up with other things MS have been trying to do recently to gather as much personal data as possible from users to feed their AI efforts.
Their spokes person also avoided answering why they are doing this.
On the other hand, you comment seem to be trying to reach really far trying to find portray this as normal behavior.
I would have disagreed with you in the past by saying, "until it breaks something critical and you loose customers and business", but then again people just moved on from the Crowdstrike incident like business as usual.If something like that which grounded critical service globally and had an estimated 10 Billion Dollar economic impact doesn't change mindsets,I don't know what will.