To be clear, bitemark evidence is junk science. There has never been any scientific research to support the idea that bites on human skin can be matched to the teeth of one person, to the exclusion of everyone else.
And that kind of compiling of information about the materials is something other fields do that we don't do. An analogy that I would think of in software would be something like a 500-page book on how to version an API.
Take Eroom’s Law: the number of new drugs approved per dollar of R&D has fallen for decades, even as our scientific tools have grown vastly more powerful, the exact opposite of what the existence of more raw capability would predict.
My opinion is that the least mature area is front end. There have been some attempts to compile Rust to Web Assembly and then run it on the web as a front end as a replacement for TypeScript. But if I was writing a web server, I would totally use Rust for the back end and TypeScript for the front end. I would not really go the web assembly route.
That was always the idea, and that that goes back even to the predecessor of Turbo Pascal, this idea that it's not just a compiler. It's an experience, right? I mean, you don't just compile your programs. You also edit them. You also run them. You also debug them. You also have a runtime library. It all has to like fit together.
And then I also think um you know right now for matching it's like everything's done at literally the last minute. It's like someone dies, an organ comes available and like you're just kind of calling around trying to find like what patient is available to get this organ and you don't have that much time to make the optimal match, right?
By contrast, AI is increasingly matching the general cognitive profile of humans, which means it will also be good at the new jobs that would ordinarily be created in response to the old ones being automated.
I've worked a lot of companies right but I'm wrong all the time and I think consumer behavior can be very fickle and especially when you work at a company you become a power user naturally. So sometimes you you may forget like what the actual user experience is for a brand new user.
But really the software engineering agents I think can be done faster sooner than any other agent because it is a verifiable domain. You can always unit test or compile, and there's many different regions of it can inspect the whole code base at once, which no engineer really can.
I’m also still not sure how much I like nix – it’s very confusing! But it’s helped me compile some software that I was struggling to compile otherwise, and in general it seems to install things faster than homebrew.
Their words now
I’ve mostly switched back to Homebrew, nix was interesting but overall I think it’s not worth the complexity for me
The cost to discover and develop a drug today is orders of magnitude higher than in the 1950s. Despite this, the probability that a drug entering clinical trials will eventually reach the market has hardly improved in the intervening years.
Whether one does find a good spouse or not depends more on one's orientation towards actually building relationships, and whether they can identify non-trivial traits in a partner that would contribute to that.
Here we show that scaling up language models greatly improves task-agnostic, few-shot performance, sometimes even reaching competitiveness with prior state-of-the-art fine-tuning approaches.
A korrent is a belief a person has stated in their own words: one
sentence stating the claim, backed by a quote and a source, kept at
korrents.com.
Under a name here, the quoted block is what they actually said.
The korrent beneath it is the claim those words support, in
korrents' wording — tap it to see the record, its source, and who
else holds it.
Nobody here wrote their own korrents. They are compiled from public
statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they
do, this site shows a machine translation beneath the post, in
this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the
serif above is exactly what the person published, and it is what to
quote them on. A translation can be wrong in ways that matter,
especially about tone.
Only the post's own words are translated. A quoted post, a linked
article and a belief on korrents.com
are left in their original language.