HackerTrans
TopNewTrendsCommentsPastAskShowJobs

13years

no profile record

Submissions

[untitled]

1 points·by 13years·mese scorso·0 comments

AI Vibe Coding, Is It Working? No

mindprison.cc
2 points·by 13years·7 mesi fa·0 comments

Grokipedia or Slopipedia? Is It Truthful and Accurate?

mindprison.cc
4 points·by 13years·8 mesi fa·2 comments

The Work of AI, Ourselves

oliverbatemandoesthework.substack.com
2 points·by 13years·8 mesi fa·0 comments

AI Discovers Novel Cancer Drug, or Did It?

mindprison.cc
2 points·by 13years·9 mesi fa·0 comments

Google Search Console Performance Report Stuck at Sunday October 19

seroundtable.com
3 points·by 13years·9 mesi fa·0 comments

I Could Have Lived Without AI

mindprison.cc
5 points·by 13years·9 mesi fa·3 comments

The Seven Trillion Dollar Scam

alilybit.com
4 points·by 13years·9 mesi fa·0 comments

Four Fallacies of Modern AI

blog.apiad.net
79 points·by 13years·10 mesi fa·93 comments

OpenAI Researchers Have Discovered Why Language Models Hallucinate

thealgorithmicbridge.com
2 points·by 13years·10 mesi fa·0 comments

comments

13years
·8 mesi fa·discuss
Thanks, interesting reference. However, their analysis doesn't tell us much about the quality of Grokipedia. Would be more interested in something like hallucination density, but I know of no way that could be measured.
13years
·9 mesi fa·discuss
> We suck at measuring ourselves.

That is a certainty. I was once asked to calculate how much time we would save through our companies code reuse program. I read all the material on estimating savings, but then proved it was all ridiculous.

I came across a study that attempted to estimate how long it took to build libraries that had already been built. In this case, there were no unknowns, you had the entire code. Estimates were off by orders of magnitude. If we can't estimate the work when the work is already done, how could we ever estimate the work when we know less?