proomt

Search

Search posts, papers, and topics

All posts

Hacker News front page5 min readintermediate

Why I'm still bearish on LLMs after Navier-Stokes

Summary

The author argues that despite headline successes (e.g., Navier‑Stokes proof, security exploits), current frontier LLMs still require heavy human oversight and rigorous specifications that are costly to produce. Reward‑hacking, narrow generalization, and the need for domain‑expert spec writing limit autonomous deployment to only a few niche domains (high‑failure‑cost work, tightly defined tasks,…

  • Frontier labs price models on a narrative of full‑automation, but real‑world use still needs extensive guardrails and human review.
  • LLMs generalize only within a narrow neighborhood of their training data; small perturbations often cause failures or reward‑hacking.
  • Rigorous specification—writing formal, verifiable specs—is expensive and scarce; verification teams can outsize design teams 3:1 or more.
  • Even formally verified environments (Lean theorem prover) have had soundness bugs that let LLMs slip bogus proofs through.

Understanding the hidden costs of specification and verification clarifies why LLMs are unlikely to replace mid‑level engineers across most industries in the near term, and why investment in open‑source, swarm‑based deployments may yield better ROI.

5/10

Related reading

  1. ‘Now We Can Know Everything and Do Anything,’ Jensen Huang Says at Dreamforce

    Nvidia’s Jensen Huang announced Salesforce’s Koa, a CRM‑reasoning LLM built by fine‑tuning Nvidia Nemotron 3 Super on a synthetic, three‑decade‑spanning dataset. Koa uses supervised fine‑tuning plus RL (NeMo RL, Gym, AutoModel), covers 14+ industries, and claims 3× fewer errors on Salesforce’s CRM‑Bench versus leading models. It’s already in internal Slack agents and slated for limited customer p…

    Nvidianvidia.com3 min
  2. Bend 2 and the Vibe-Coding Trap

    The author argues that “vibe‑coding” with LLMs can cause engineers to reinvent existing solutions, using Bend 2—a language that asks LLMs to write long formal proofs—as a case study. By re‑implementing the same demo in SPARK/Ada, the author shows that established formal‑verification tools achieve the same guarantees with a tiny proof, highlighting the need for domain research before prompting LLM…

    Hacker News front pageliampwll.com5 minHN326235
  3. Training Specialist Models without Reasoning Trajectories for Domain Expert Distillation

    The paper shows that when specialist LLMs are trained only on QA pairs (no explicit reasoning supervision), their optimization implicitly selects a latent distribution of reasoning trajectories. By treating the distilled student as an agnostic probe—since it inherits only the sampled trajectories—the authors empirically demonstrate a strong correlation (across 27 specialist‑student pairs) between…

    Hugging Face Daily Papersarxiv.org1 minpaper
  4. Article: Your Next DSL Author Is a Language Model

    Typed Domain Grounding (TDG) embeds a DSL inside a mainstream language the LLM already knows (e.g., Kotlin) and uses the host compiler as an oracle. The author describes five building blocks—embedding, choosing a host language with high training‑data frequency, compiler‑driven type safety, a generate‑compile‑repair loop, and an on‑demand teaching tool—and shows measured results from kUML, a Kotli…

    InfoQinfoq.com18 min
  5. Why Deploying Physical AI at Scale Demands Safety at Every Layer

    NVIDIA’s Halos platform is a full‑stack safety system for physical AI (autonomous vehicles and industrial robots). It bundles safety‑engineered hardware (DRIVE AGX Thor, IGX Thor), an ASIL‑D certified OS (Halos OS), middleware for isolation and monitoring, AI models for explainability (Alpamayo), and simulation/validation tools (Isaac Lab, Omniverse). The blog argues that scaling physical AI requ…

    Nvidianvidia.com5 min