4 ms·
Is editing code really the endpoint for llms? I suspect we'll be getting to a point where the "code" is just instructions, codified in a special markup file, a
by almosthere 2y ago
Is editing code really the endpoint for llms?
I suspect we'll be getting to a point where the "code" is just instructions, codified in a special markup file, and llms just write the worst possible, kiss code you can think of - but is extremely secure because it's just like direct database access with all the security constraints you define, but always applied correctly. In other words think of the actual code as a non-committed artifact, and it's just emitted if the descriptors change.
The long term of llms writing code isn't to give us human quality code, it's to give us what we'd think of assembly but rigorously output to all auth requirements.
- rzz3 2y agoBut, the need for reproducible and auditable code will remain. If I take your idea full circle, first we’ll have this committed set of English prompts, then we’ll need to evolve some type of very explicit structure around the prompts to ensure the LLM interprets it exactly in the right way, then we’ll want to make the instructions more efficient and easier to type than a long paragraph of English text, so we’ll create a more condensed markup syntax, and then we’re right back at… a programming language.
- almosthere 2y agoThe long term of programming languages is to make it higher and higher and higher level, so LLMs may be the next iteration. We'll start seeing things like Java, Python and Ruby code as we see Assembly now, and the structures you're describing as the program.