NHacker Next
  • new
  • past
  • show
  • ask
  • show
  • jobs
  • submit
Why Problem Statements Aren't Enough (letters.unchartedpathbreakthroughs.com)
oliculipolicula 2 days ago [-]
TFA has 2 Qs aimed at building trust-culture:

>Who has the missing context?

>If the work succeeds, what changes beyond “the project shipped”?

As a total rando trying to develop a (possible) nothing-burger I call expert embarrassment, I'd derive 2+2 corresponding what-ifs:

What if

  1. nobody in the org does?

  2. the project ships yet nothing changes?
Excuse my extra what-ifs for being kind of sly takes on the class of "Maserati Problems"

https://dfccyyqjngn5p3.archive.ph/uWeuT/2f4f3d465f8a85a41e89...

  3. What if we don't market our solution?

  4. but it still blows up in our face?
(MPs being defined by the context that makes their technicality _seem_ reasonable only long after you'd have acquired one, but your ability to answer them matters _now_

Here's a real world instance, related much better than I ever could

https://www.cringely.com/2026/05/28/the-permission-slip/

)

Chu4eeno 39 minutes ago [-]
> https://www.cringely.com/2026/05/28/the-permission-slip/

That anthropomorphized misunderstanding of what "hallucinations" actually are (and how he supposedly could "solve" it) is pretty embarrassing.

Someone else wrote more eloquently than I'm able to about it: https://news.ycombinator.com/item?id=48725262

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact
Rendered at 12:33:06 GMT+0000 (Coordinated Universal Time) with Vercel.