Feel like those are more akin to science philosophy than concrete scientific understanding. Which tends to happen in scientific pursuits when we dig deeper than what we can realistically actually explore in a strictly scientific way. Biggest problem is we struggle to recognize it as philosophy when it comes out of scientific thinking. We *want* to know more than we can piece together through scientific basis and for lack of a better option we go for the unfalsifiable and subjective opinion.

I recall a physicist explicitly addressing the phenomenon in his field. He refrained from participating in the musings because all he could do was figure out what math worked and hope someone comes up with better math, the wilder speculation upon unobservable implications was beyond the scope of what he felt science could do, but it's a very popular thing in physics.

I perused the paper, I think the comment was pretty spot on. Specifically the part where they have as a casual assumption that they know how human consciousness works.

It's basically shaking the magic 8 ball and it works, but it's totally a judgement call when it has worked 'enough'. It doesn't necessarily progress from easiest to hardest issues to find, it just is a bit random. Hard to say how many passes before you've *probably* got the real ones. My experience has not been that false positive rate increases, sometimes you might have all false positives but a continuation will flag real issues.

Indeed, they take needles in haystacks and make smaller haystacks that have some of the needles. They don't catch some things and they falsely flag a lot of things, but they do either directly or get close to something.

One issue in our codebase that was caught was pretty much spot on. Now upon it being highlighted, it was obvious to anyone that the inexperienced developer screwed up, problem was no one had the attention span to notice. The other issue close to real that it caught was actually not the flaw it indicated, however while looking at the jankiness that caused it to mis-indicate, a real issue was discovered. So it's indicated "fix" would have done nothing and left the codebase vulnerable, but the finding *was* useful in identifying an actual problem and fix.

However, it does open up a gigantic mess in customer engagement. Customers like to use every security tool at their disposal and hold the vendor accountable. Fine, except now we are inundated with false positives because the LLM indicates something, the customer has no way of knowing if the LLM is right or not, and we have to address false positives. We are now having to consider how to "fix" false positives by steering the LLMs away from indicating bogus things when analyzing our product. When it was the occasional misguided security researcher making a misunderstanding, no huge deal, we could discuss nuance and come to an accord. With the LLM mess, there's no skilled human to appeal to, a skeptical customer, and just a lot of volume...

Whatever you may think of capabilities, the narrative has always been about what they think sounds best in the moment.

So at one point, only the owner class matters, investment is King and every other concern can be bulldozed. The business opportunity down market would never be as much as what employee replacement would be.

Now they see a need to balance it because shockingly the people still have some leverage, whether it's banning construction projects or getting skittish with retail investment. Further the stories around employee replacement have gone permanently bad at prominent companies like Ford. So they need to move the goal posts to dodge the negative optics and recalibrate expectations.

I cannot agree more with this sentiment. It feels outright insulting to asked to read LLM output in a context where it is *supposed* to be human feedback. Tell me what you would have told the LLM to say, I can take it from there. I don't need you to LLM it up, because it will bury your point in a bunch of crap.

Could it provide useful info? Maybe, but I can do that myself if so. I want *your* thought on something, however incomplete it might be.

The dream is that the world is built for human limbs and the 'easiest' answer to claim the same versatility is to also have human limbs.

Stairs, cluttered terrain, a humble curb can all cause problems for the usually better answer of wheels.

The non-humanoid robots we already make those by the ton, and are, as one would predict, much more useful than human-like anatomy in their context. They however want to cover the underserved facet, banking hard on ML to make the humanoid design more viable while they traditionally are just infeasible to program.

Of course, that has proven a challenge, since the ML needs to instrument all the inputs and outputs of a human interaction system, and feeling is a huge part of human operation that cannot be instrumented. So they set people about trying to clumsily remote operate them in hopes of gaining training data, but it's low quality control and very low volume of data.

The disconnect is the "promise" is that LLM brings expertise down to the masses. If AI is "too hard for Ford to get right", that dramatically undermines the messaging that drives the current expectations and levels of investment.

This is very much evidence that companies can't be as bullish as they might inclined to be, because whatever you may think of Ford, the typical company is probably worse.

It's less funny when you have people literally and sincerely saying this...

I have to take some solace in the fact that these are the same idiots who talk a lot and do nothing that I usually ignore who do this all the time, but management is extra entranced with them over the AI cheerleading this go around...

Maybe for starting their own businesses, but I don't think just to compensate them for having to take a job that's "beneath them". Like you indicate, if another person makes $15/hour and didn't get a handout because they never made money, it would seem awfully unfair to give someone more money because they used to make more money. Easy to argue that the person coming down should by all logic have more financial resources already than the folks working the jobs. If their lifestyle based on higher income is infeasible with available jobs, think the reasonable sentiment would be "tough". Sell that car and settle for something more modest or take a bus, the same sort of compromises the lower paid coworker has *always* had to make. I suppose if anything, some financial relief for those trying to support a college kid where scaling the lifestyle down isn't as straightforward, but broadly speaking they don't have a particular right for government to help them more than they help peers that never made a lot in the first place.

Keep in mind it's not and hasn't been a specific measure of something in particular in a while. It's a rough analogy for how a traditional process would have to make gate length to achieve the same density. So it's impossible to make a gate length that small, but by taking other measures it is supposed to be "just like getting them that small".

AI is stupid, but it can track details and at least provide a hint.

On the "make stuff that works" side, I've had the experience like yours. If someone lets it go too far, then it's a headache and it's easier to roll it back. If anything a bit painful as it's "empowered" some of the worst to make my day harder, being confidently incorrect all the time.

On the "find stuff that's broken" side, well, humans don't have the attention span and the AI techniques are catching little but critical mistakes by humans. In my codebase that has had regular security reviews for over a decade, including a few outside consulting companies, this year marked the first year that the teams had LLM at their disposal. It found two security issues that no one had noticed, one of which had been there almost essentially from the beginning. Admittedly, neither were exactly world ending (both required attacker to log in with admin privileges and the things you could do were a bit constrained), but they were real and undesirable. One of them kind of missed the point and although it mis-characterized the behavior, it put a light on an area where a human could actually think through and sort out the real issue, and how the flawed approach applied more broadly than the AI identified.

So AI as a review tool can work, it has a significant amount of false positives and misses stuff of course, but it can either directly catch or inspire human attention on a sketchy area.

The security team said that it was actually quite remarkable they only found two vulnerabilities that both required admin access, that most projects they dealt with ended up with 4-5 vulnerabilities exposed to either unprivileged users or even unauthenticated access. This is the sort of code the world is mostly built on.

Presumably, this is the whole point of these contracts, to hold the customers accountable for Micron making memory for them when the broader market is not necessarily looking for that particular memory.

Now I don't see how this can work out in one of the more well documented ones. OpenAI had at least a trillion dollars of these sorts of purchasing commitments, and even pretty bullish assessments don't support their ability to make that much purchase. So I do anticipate the market failing to make their minimum purchase commitments. I'm presuming there are penalties in these agreements and so they probably get money for nothing unless it gets so bad that OpenAI goes actually bankrupt.

It uses a screen as a gauge cluster, and puts the backup camera feed there.

They don't presume any speaker setup either, which would be a pretty key expectation of android auto in general.

They evidently will support a double-din mount of whatever you want, so you could add that without much issue.

Presuming reasonable access to channels to cable and mount speakers, I'm a huge fan of this facet of things.

I would like to see a couple of integration points, steering wheel controls and EV battery state/range estimates fed to the navigation like you get with other EVs and android auto, but no need to be as heavy handed as other platforms.

Unfortunately for my situation, it would lose out handily if a competitor had a midgate. I rarely need a substantial bed and usually need the seating, but it looks like it won't be easy to free up your bed if you have the seats in. Also subjecting the rear passengers to coming in by the front door.

If slate had a 4 door pickup with midgate to get longer bed, and maybe 20 inches or so longer to have that same bed even with rear seats available, I'd strongly consider it.

You do know that if the immune system got confused about virus versus cells hijacked to replicate viral material, we would have been dead pretty much the first second you got exposed to a virus? This is what a virus does. The difference is the virus produces material that will re-infect cells, while the mRNA resultant material is not self-replicating.

You also know that we had *billions* of people use mRNA vacinne and autoimmune problems weren't even vaguely a concern, and it was effective?