Live data from Hacker News

Viewing profile — beshrkayali

beshrkayali

HN member
Joined
Sat, Apr 03, 2010, 7:17 AM UTC
HN karma
3,336
Public activity
600 items

About beshrkayali

No profile information was provided.

Recent public activity

  1. comment
    Comment #48870372

    This is hilariously true > AI risk is string theory for computer programmers. It's fun to think about, interesting, and completely inaccessible to experiment given our current tech…

  2. comment
  3. story
  4. comment
    Comment #48525287

    Should’ve probably said “attempted at defining” instead of “defined”.

  5. comment
    Comment #48525207

    It can’t, unless you descend into sophistry. We came up with and defined the word “consciousness” specifically to fit our own understanding of the collection of behaviors we do tha…

  6. comment
    Comment #48285263

    In the case of Claude or others, it is not just an advertisement, it's the weird shape the industry is spinning LLM-assisted-coding as a "co-author" relationship where it should be…

  7. comment
  8. comment
  9. story
  10. comment
    Comment #48137192

    > But they’re hamstrung by the terminal itself, which is almost always monospaced and thus fatiguing to read. Not related to the main point of the article, but I find reading long …

  11. comment
    Comment #48104945

    Everyone is trying to figure out how and what are the optimal use cases. It could be like you said but it doesn’t have to be. There’s a lot of incentive for it not to end up like t…

  12. comment
    Comment #48104858

    For now it’s the exact same reason why you’d use Python when you’re writing by hand: so the code is more easily readable/editable by humans who are more likely to know Python than …

  13. comment
    Comment #48061579

    Humble mention, I’ve been thinking the same thing with Ossature for the last couple of months since I started working on it: https://ossature.dev The models are already good enough…

  14. comment
  15. comment
  16. comment
    Comment #47994839

    I wrote something similar recently about how agent-generated code lacks the institutional memory that human-written code has. There's nobody to ask why a decision was made (1). “Sp…

  17. comment
  18. comment
    Comment #47986906

    The title of the article is more on the sensationalist side unfortunately, the actual paper gives a different view [1]. There are two parts worth quoting: > Although cortical reduc…

  19. story
  20. comment
    Comment #47658284

    Exactly, and it is a DAG (specs and tasks in the toml plan). Check the QOIzig example and its task graph if you’re curious!

  21. comment
    Comment #47653271

    Exactly this. The audit pass in Ossature is specifically for that "unclear spec" case, you resolve ambiguities in the spec before generation starts rather than discovering them mid…

  22. comment
    Comment #47650077

    Allium looks interesting, making behavioral intent explicit in a structured format rather than prose is very close to what I'm trying to do with Ossature actually. Ossature uses tw…

  23. comment
    Comment #47649570

    All three of these are real. The audit pass in Ossature is meant to catch the first two before generation starts, it reads across all specs and flags underspecified behavior, missi…

  24. comment
    Comment #47648154

    Very much the same thinking. Ossature already structures work that way at the plan level during audit, so curious to see where you take it. Happy to share more about the TOML appro…

  25. comment
    Comment #47648112

    The hierarchy you describe (intent -> plan -> code -> tests) maps well to how Ossature works. The difference is that your approach builds scaffolding around Claude Code to recover …