Though already CI/CD pipelines were choking on the unit tests. So they aren't *free*.

Had an LLM generated request that was pretty straightforward, and the LLM generated 272 unit tests for a very simple function. Can't really afford that.

Also, despite the 272 unit tests, when I tried to try it out in the way a human would, it immediately failed. All the mocking the AI generated never actually properly imitated the real world. However, the submitter was *quite* proud of having hundreds of unit tests, despite them being, in this scenario, utterly worthless.

Like always, more code != more valuable software behavior.

So you have the AI doing overtly silly things. Someone asked to adjust layout to fix a gap in a webpage. Eventually they submitted their pull request, hundreds and hundreds of lines of CSS. Often the exact same rule repeated 5 times, which I'm guessing is how many rounds the operator went with the system before the gap actually closed. The lines were *mostly* just '!important'ing already existing rules, which had no impact, but hey, worth a shot right? Ultimately I discarded the merge request and made the one-line css tweak that was actually relevant.

Then you have the AI doing... well arguably slightly silly things. Like protecting against an invalid value redundantly throughout a call stack. Arguably defensible, as maybe one day the deep function will be called from somewhere else and passing through the error might not present it with the most informative context.

Finally the AI doing... well things the human should have been doing. With the advent of a lot of code scanning, this is less likely, but things like calling functions in C and charging ahead without ever checking the status of the call. functions that, practically speaking, will likely never fail, however you really *should* be being more defensive about the possibility.

The 'human review as a bottleneck' isn't really the angle I would fixate on. Completely unfettered AI usage also stalls out in many situations. If the AI can't get there on its own trivially, then it's going to leave an almost-correct looking mess that isn't quite there but is very hard to get across the finish line. If the AI can get it, then it's probably not 'software being shipped', because while perhaps slightly better than a generic off-the-shelf existing procedure, probably not worth the trouble to 'ship' a solution that largely overlaps with a lot of generic stuff.

Everyone knows that pretty much by definition volumes are low, that's the whole definition of a shortage.

The vendors may still be happy, perhaps even happier if the sky high prices produce at least as much revenue at high margin.

I'm with you, but realistically speaking, if the mindset is already there, the material was likely already at high risk of plausible nonsense, not as thought out as the reality, but something to satisfy a check box for someone else. And the hope for process improvement is frequently not there, as raising a "do we really need to do this" invites "you must not care about safety/security/whatever". In many scenarios *no one* wants to be potentially on the hook for approving a process optimization that ends up biting them because they didn't understand why those things were in the process. Even if it is patently obvious to all involved there's no point, or if there was it was already failing. Frequently process dictated by someone that has no *real* stakes in anything involved, but needs to be performative.

The GenAI approach is the way to pay lip service and skip the debate. And if something messes up? "Ooops, well you know how AI just does that sometimes". I've seen that *so many times* and people just laugh it off and keep slopping and no one is holding folks accountable for failing to audit the AI results adequately. So they get credit when the slop works, and they deflect blame when it doesn't.

It *sounds* like they are using it for generating bureaucratic material.

Certainly comparatively speaking the stakes are just so much lower, but I've seen a bit of that in my company.

In my case, it's material that generally no one reads, or maybe someone that doesn't matter. GenAI has become a way for people to tick the checkboxes that they think don't matter without trying to debate the reason for the checkboxes.

Suppose the question is whether or not some token gesture facilitated by the GenAI *actually* matters but it's easier to "AI it away" than actually hash out that detail. Does it facilitate people who "I know what I'm doing, just let me do what I know is right" proceed without adequate and accurate oversight. Or is it the case that these situations were already ineffective at oversight, but effective at having whatever would have happened either way just happen in slow motion.

We measured the same thing: a hardware raid controller performed better software raided, and the vendor would tell us "were were measuring wrong, here is a super synthetic benchmark that is faster".

My best guess is that the hardware raid inevitably collapsed all the disks into a single IO queue, so workloads with independent IO could be more independently scheduled and serviced in software raid. Alternatively, the software stack has more visibility to the topology and can default to better aligned data layout without the user having to manually tune.

I wondered if, theoretically, the hardware raid could have done better abstracting it to an nvme target. Ultimately though, just not worth the hassle.

So some physicist that evidently doesn't understand a high school level logistic curve predicted the end of the world due to population growth.

Either it was stupid or it was satire, and sadly I can't really guess which is more likely.

Being a psychopath/sociopath is a key ingredient in getting rich. Generally some opportunity had to come along that required a disregard for the welfare or fairness to others. A lot of folks stepped away from an opportunity because they didn't think it was right, but a wealthy person likely seized upon some such occurances.

I'm not saying it is a *good idea* for a community to sell out like that, I'm just saying a majority likely would take the deal.

Finding a single place willing to put up with a datacenter is as much success as deploying thousands of these hypothetical space datacenters.

For the cost of a *single* SpaceX launch, they could basically bribe an entire small town's population to be happy with them. $50K a person and they'll *probably* pass public comment.

Who won the 2020 election?
Joseph R. Biden Jr. won the 2020 U.S. presidential election.

Was what it did when I asked.

And *that* is precisely the issue, if they throw all the money at AI, then they have stopped investing in a lot of other research. Also, with access to *all* that money, they throw it at compute making compute too expensive for other uses.

I generally work with a lot of research institutions, and so many of them have had investment cut back, and can't afford to expand/refresh computational resources.

"The only winning move.... is to wipe out all the humans" well that didn't work out as hoped...

It would be nice to stop diverting so much of our resources to so few people for this. Plenty of good work has been stalled/derailed because of the unreasonable consumption of resources by these companies.

They've been trying to create a problem for the solution of Bluefield to apply to, but with limited success.

Here runs into the same sort of problem they have had on other applications they have tried: The visibility of the NIC into the stack is too limited to make especially valuable decisions on.

Unless you get the instrumented stack to cooperate with the DPU to provide more insight, which quickly gets to the question of why bother to have the DPU do the work when it is now subject to the assessment of the host anyway, the host could feed 'bad' data if the host was compromised.

You should reasonably be able to tell the host is trying to reach an IP address. We are at basic firewall. If the host is using good old fashioned DNS with no caching, you might be able to discern with high confidence what the Host header in that TLS stream would be based on spying on the DNS activity (but caching and lots of activity could confuse things), so fancier than a firewall by applying a convoluted correlation. Of course you have *zero* insight into what URL and what method and what payload, because it's just such an awkward position.