Re:Learning from Failure to Tackle Hard Problems
by shermantanktop on Wednesday November 05, 2025 @03:55PM
(#45827876)
You're describing bruteforcing through repetition. The paper is essentially about increasing the chance of success by training model which learns on failure.
That may not apply to a building a viable company directly. It might suggest that new companies should avoid replicating elements of failed companies.
Re:Learning from Failure to Tackle Hard Problems
by LPisGood on Wednesday November 05, 2025 @01:00PM
(#45825850)
I had a professor in an additive combinatorics class that would (when appropriate) say “hint: it’s easy” and as silly as it is, it usually helped a lot.
Re:Learning from Failure to Tackle Hard Problems
by Nevermark on Wednesday November 05, 2025 @01:38PM
(#45826253)
I worked on a problem for a couple months once. As soon as my professor hit mid-sentence telling me he found someone with the solution, I rudely blurted it out.
My mind was so familiar with all the constraints, all I had to know was that there was a solution and I knew exactly where it had to be.
But before knowing there was a solution I hadn't realized that.
Re:Learning from Failure to Tackle Hard Problems
by paulorlando on Wednesday November 05, 2025 @03:07PM
(#45827267)
While Bannister’s 4-minute mile record is used as an example of a psychological barrier, there’s also a reinterpretation of the meaning behind his record. Before his 1954 race, the record for the mile stood at just over 4 minutes (4:01.4) for 9 years. While speed records were set during WWII, they were all set by Swedish runners (Sweden being neutral in the war). The record today, which has stood since 1999, is 3:43.13. It's not a round number, so as a result gets less attention. Maybe that's why we don't think of it as a psychological barrier.
Re:Learning from Failure to Tackle Hard Problems
by mcmoor on Wednesday November 05, 2025 @11:36PM
(#45831530)
Reminds me of barriers in speedrunning. Technically all the times are arbitrary, but there's still prestige to be the first person to get under <nice number>. I don't think it really influences the speed of record breaking around it, except that time when there's literally a bounty raised.
Re:Learning from Failure to Tackle Hard Problems
by abtinf on Wednesday November 05, 2025 @12:09PM
(#45825238)
> The [goal] of machine learning research is to [do better than humans at] theorem proving, algorithmic problem solving, and drug discovery.
Naively, one of those things is not like the others.
When I run into things like this, I just stop reading. My assumption is that a keyword is being thrown in for grant purposes. Who knows what other aspects of reality have been subordinated to politics by the writer.
Re:Learning from Failure to Tackle Hard Problems
by dgacmu on Wednesday November 05, 2025 @12:56PM
(#45825807)
These have all been stated as goals by various machine learning research efforts. And -- they're actually all examples in which a better search heuristic through an absolutely massive configuration space is helpful.
Re:Learning from Failure to Tackle Hard Problems
by qqxufo on Wednesday November 05, 2025 @01:41PM
(#45826285)
Failure doesn’t teach by default; it teaches only when you design for it. Three dials matter: cost, frequency, and observability.
Make failures cheap and reversible. Shrink the scope until a rollback is boring. If a failure requires a committee or a quarter to undo, you’ll avoid the very experiments you need.
Raise frequency deliberately. Schedule “bad ideas hour” or small probes so you don’t wait for organic disasters to learn.
Max out observability. Before you try, write the few assumptions the test could falsify. Log what would have changed your mind earlier (counterfactual triggers), not just what happened.
Two practices that compound:
1. Pre-mortem → post-mortem symmetry. In the pre-mortem, list concrete failure modes and “tripwires”; in the post-mortem, only record items that map back to one of those or add a new class with a guardrail/checklist—not “be more careful.”
2. Separate noise from surprise. Tag outcomes as variance vs. model error. Punishing variance breeds risk aversion; fixing model error improves judgment.
Hard problems rarely yield to heroics; they yield to lots of small, instrumented failures.
Re:Learning from Failure to Tackle Hard Problems
by chrisXOXO on Thursday November 06, 2025 @05:46PM
(#45841433)
That idea feels really relevant to me as a future research direction(not an expert). Could maybe someone explain what I am missing here? Why does this idea not get more attention?!
Is it not new? And if so, could one state why it is not commonly employed?
Take building a viable company. You know that many people have solved this. But you also know that 9/10 fail.
So you need the time and the money to try enough times to make it work.
https://clarifycapital.com/blog/what-percentage-of-businesse...
That 80% number is after 20 years. That's far longer than almost anyone stays at the same employer. Maybe if those failures are the owners retiring.
You're being lied to. The myths of silicon Valley are not there for the benefit of founders.
That may not apply to a building a viable company directly. It might suggest that new companies should avoid replicating elements of failed companies.
My mind was so familiar with all the constraints, all I had to know was that there was a solution and I knew exactly where it had to be.
But before knowing there was a solution I hadn't realized that.
343 is 7 cubed, so just call it "cube barrier!" and it becomes a worthy challenge
Naively, one of those things is not like the others.
When I run into things like this, I just stop reading. My assumption is that a keyword is being thrown in for grant purposes. Who knows what other aspects of reality have been subordinated to politics by the writer.
Make failures cheap and reversible. Shrink the scope until a rollback is boring. If a failure requires a committee or a quarter to undo, you’ll avoid the very experiments you need.
Raise frequency deliberately. Schedule “bad ideas hour” or small probes so you don’t wait for organic disasters to learn.
Max out observability. Before you try, write the few assumptions the test could falsify. Log what would have changed your mind earlier (counterfactual triggers), not just what happened.
Two practices that compound:
1. Pre-mortem → post-mortem symmetry. In the pre-mortem, list concrete failure modes and “tripwires”; in the post-mortem, only record items that map back to one of those or add a new class with a guardrail/checklist—not “be more careful.”
2. Separate noise from surprise. Tag outcomes as variance vs. model error. Punishing variance breeds risk aversion; fixing model error improves judgment.
Hard problems rarely yield to heroics; they yield to lots of small, instrumented failures.
Clearly didn't send the article to the LLM.