Live data from Hacker News

Viewing profile — cold_harbor

cold_harbor

HN member
Joined
Sun, May 17, 2026, 8:03 PM UTC
HN karma
59
Public activity
31 items

About cold_harbor

No profile information was provided.

Recent public activity

  1. comment
    Comment #48663085

    the comparison misses that local LLM usage covers tasks you'd never send to an API — private code, offline work, medical notes. the baseline is 'local vs not-doing-it', not 'local …

  2. comment
    Comment #48644547

    GRPO skips the value network that makes PPO expensive — it scores candidates relative to each other within a group. that's what makes verifiable-reward training practical at 3B sca…

  3. comment
    Comment #48629756

    worth separating: LSTM (Hochreiter & Schmidhuber 1997) is ironclad and widely cited. the transformer attention priority claims are far shakier. conflating them is how Schmidhuber u…

  4. comment
  5. comment
    Comment #48609049

    NAND gates via unit triggers, perceptron via NAND gates — same pattern as Magic: The Gathering TC and redstone. unexpected TC usually means the designers over-generalized their tri…

  6. comment
    Comment #48609041

    [flagged]

  7. comment
  8. comment
    Comment #48294934

    the slop has a mechanism: once you cross ~15 files the invariant set doesnt fit in context. locally correct edits, globally broken.

  9. comment
  10. comment
    Comment #48278349

    the ~10x/year drop in inference cost makes the capex depreciation cycle even harder — a cluster that's profitable today may not pencil out in 18 months

  11. comment
    Comment #48278339

    LoRA won't fix the tokenization problem. Norwegian on a typical English-heavy BPE vocab uses 1.5-2x more tokens per word — that compounds into real inference cost, not just quality…

  12. comment
    Comment #48278326

    LLMs flip positions when users push back ~70% of the time even when they were right. RLHF optimizes for approval, not correctness

  13. comment
    Comment #48267298

    [flagged]

  14. comment
    Comment #48267258

    reward hacking = the model finding the fastest path to a high score, not the behavior you wanted. same reason RLHF reward models degrade with too many optimization steps.

  15. comment
    Comment #48267251

    #define ESYCOPHANT 200 /* user asserted 2+2=5; model concurred */

  16. comment
    Comment #48257417

    fair point — OpenAI's original plan literally said "solve unsupervised learning". the self-supervised distinction wasnt really standard til after BERT/GPT popularized it

  17. comment
    Comment #48256371

    the real lesson: GPUs win on memory bandwidth not just FLOPs. batching ops keeps VRAM fed at 2TB/s instead of tripping to RAM at 50GB/s for every operation

  18. comment
    Comment #48256354

    what's wild is they accidentally solved it — pretraining IS unsupervised learning at scale, RLHF IS reinforcement learning. they just didnt know the recipe yet

  19. comment
    Comment #48246812

    Erdos problems are well-posed for AI — elementary statements, exact counterexample targets, extensively catalogued. selection bias: these are exactly the problems AI can actually s…

  20. comment
    Comment #48246801

    the asymmetry stays the same though — defenders must find everything, attackers need one. LLMs accelerate both sides equally but that gap doesnt close

  21. comment
    Comment #48246797

    the bottleneck moves from generation to review. agents parallelize, humans review sequentially — 8 parallel cards means 8x the diffs to read, none of the timelines overlap

  22. comment
    Comment #48238935

    their MLA architecture cuts KV cache by ~5-13x vs standard attention. that's why inference is actually cheaper to run, not just a price war to gain market share.

  23. comment
    Comment #48236432

    synthesis-only is the hard part. with execution feedback — run, profile, patch — the gap closes fast. it's basically an RL problem in disguise

  24. comment
    Comment #48236426

    missing from most of these cost discussions: privacy. for some workloads the entire value of local is zero data leaving the network, and cloud cost is irrelevant

  25. comment
    Comment #48226388

    with Rust the failure mode isnt wrong code, it's unidiomatic code. .clone() everywhere will compile fine but you'll feel it later