alt Hacker NewsIt's not about the prompt, it's about the guardrails. Static types, compiled, massive test suite, etc. That what I mean by extreme level of test coverage like SQLite. You'd actually need to be an expert in C and SQLite and the SQLite test suite just to sneak a bug into it. Testing and other verifications are going to be an exciting area for the foreseeable future.
You can still write non-performant code even with tests, but you can also test performance!
Am about as far away from a C expert as one can be (and probably want to keep it that way for the time being), so happy to take your word on that front. Still feel, it'd be easy and in their interest for one of the major labs to provide a verifiable showcase/research paper on that front. Zig-to-Rust in Bun is the closest and that is very impressive, but I feel it doesn't necessarily map to new features/changes beyond porting. The compiler, browser, etc. all equally do not fill me with that much confidence, but perhaps in SQLite modifications could be hard for a model to mess up.
What I will say is that I feel valid in saying that the developer behind gas town (a shudder runs down my spine even having to think about that) is not working in a test suite anywhere comparable to SQLite, though in fairness, you never claimed that.
Again, you are likely not wrong that with an environment like SQLite, bugs may be hard to sneak in, but then again, isn't retaining that so important that it is a strong argument for developers auditing LLM output even more strictly, lest we loose the resilience we currently have?