If you want your agent to be really good at working with dates in a functional way or know how to deal with the metric system (as examples), then you need to train on those problems, probably using RFT. The other challenge is that even if you have this problem set in testable fashion running at scale is hard. Some benchmarks have 20k+ test cases and can take well over an hour to run. If you ran each test case sequentially it would take over 2 years to complete.

Right now the only company I'm aware of that lets you do that at scale is runloop (disclaimer, I work there).

Now we're in a situation that's so much worse than I ever imagined -- Trump coins are vehicles for naked bribery and corruption with a sprinkle of encryption on top. I was worried about black markets, Trump has literally been using his office to grant access to top holders of his scam coin.

This is a big lesson for everyone about why some degree of regulation is necessary.

This textbook is from 1929 and was probably being written at the exact same time as the Snopes monkey trial (1925). You're reading science hype because science was under attack; and not from "social justice warriors" but from conservative Americans. Notice that the single most transformative discovery in all of biology, evolution, isn't mentioned.

That attack on evolution is still taking place. In Texas there was an attempt to strike all references to evolution and climate change from the curriculum, along with other attempts to introduce biblical references. When did that take place? That was this year; oh, and in 2023: https://www.wsj.com/us-news/education/texas-education-board-...

Getting mad at "social justice warriors" for an imagined reaction while ignoring the actual attacks on science is... well, it's what I've come to expect.

Although you're right that there's likely no relationship between wives developing heart conditions and subsequent divorce, there's not enough information from the article to know whether there's anything statistically meaningful about heart conditions specifically. It seems more likely that it's just statistical noise. I read that section and got the impression that the relationship is interesting but it doesn't necessarily mean anything, rather than implying that the original study still has some validity.

By analogy, this is the same issue as frontend programming faces with the DOM. Introducing a VDOM / reducer paradigm (like react) would go a long way towards solving these problems.

I don't mean this as an insult, but after looking through your post history, you should consider psychological counseling. I recognize the coded language you are using. I'm sorry to tell you this, but you are in a cult. These people are taking advantage of you.

Into the Storm is centrally focused on the identity of Q, but in the process of pursuing the answer the creator of the documentary, Cullen Hoback, ends up going on an absolutely wild hunt. I find documentaries of this sort to be a bit hit-or-miss, but this is one of the best of its subgenre. The subculture and background surrounding QAnon is interesting in its own right but, of course, the real highlight is the characters. Fredrick Brenan, Jim & Ron Watkins, and Hoback himself are fascinating individuals.

Secondly, the person he's corresponding with, Fredrick Brennan is fascinating in his own right. He's one of the 3 central characters inside the HBO documentary, Q: Into the Storm, and has a totally bizarre relationship with Jim and Ron Watkins, the two figures currently steering the ridiculous QAnon set of conspiracy theories. It's a very strange confluence of interests.

Given how large the prize is, the next chapter of chip development is likely to be nvidia vs state sponsored projects. China, in particular, will funnel further resources into acquiring this technology by any means necessary, including (more) industrial sabotage and outright theft. It's going to be interesting to see how this will play out. Up until a few years ago China was viewed as being a formidable competitor for projects of this nature, but as the country has moved to become increasingly authoritarian, so too have its decision making and execution declined in quality.

Creditors are ranked by seniority and get paid out in order by seniority. Equity is below every creditor and has been completely wiped out. Companies are not allowed to take cash or sell the furniture to pay out employees. That money is legally owed to creditors and attempting to stiff them is theft. I'm sorry to those affected at Convoy, but that is the reality of working at a startup that goes through a hasty liquidation. Convoy is not being "cheap" about this, as some are suggesting. Any "retention bonuses" are to keep executives around for long enough to unwind the company in an orderly fashion. Nobody is getting rich off failure; if everyone were to walk away there'd be nothing left and therefore nothing to recover and distribute. It's bad for everyone, but the alternative is worse.

As for the larger situation: Convoy were a digital freight brokerage. They acted as intermediaries between shippers and carriers and make money on the spread between the two. They got into trouble because the entire freight sector has been suffering a double whammy of cost increases due to inflation (ie. diesel costs) and a slowdown in demand. This has caused a number of carriers and brokerages to go bust. Freight brokerage has some other properties that make Convoy's situation particularly serious. In particular, carriers typically securitize their accounts receivable. In freight, this is known as "factoring." Convoy got stuck holding the bag after their partner carriers went under, having already paid them for their service, but still waiting for payment from the shipper.

Worst of all, Convoy had no exits because their only potential acquirers are in the same industry and are also getting completely crushed.

JavaScript is not really a single language built around a single specific style or set of needs any more. In this day and age it's an amalgamation of different techniques and styles. You've got classic inheritance and composition for your OOP crowd; you've got your map and reduce for your functional crowd; you've even got your observables for your reactive crowd.

This is all well and good, but I've found that it's hard to write some practical code that blends styles. At some point it's tempting to start adding types, generics and dependency management into a functional project, but it's my experience that this blending ends up getting in the way of itself. Similar story for wanting to do things like having a service that listens to queues in an async way with sync rest APIs. It seems like having a common set of middleware would make it easy to support both layers; however this is easier said than done. These things sort of work but it feels deeply unsatisfying, requiring constant switching between observable and async/await styles with error handling being a constant concern.

I'm not sure which bits and pieces are included without poking through the code