Comment by Affric
7 days ago
Sure but we build (leaky) abstractions, and this is even happens in legal texts.
Asking an llm to build a graphical app in assembly from an ISA and a driver for the display would give you nothing.
But with a mountain of abstractions then it can probably do it.
This is not to defend an LLM more to say I think that by providing the right abstractions (reusable components) then I do think it will get you a lot closer.
Being doing toy-examples of non-trivial complexity. Architecting the code so context is obvious and there are clear breadcrumbs everywhere is the key. And the LLM can do most of this. Prototype-> refactor/cleanup -> more features -> refactor / cleanup add architectural notes.
If you know what a well architected piece of code is supposed to look like, and you proceed in steps, LLM gets quite far as long as you are handholding it. So this is usable for non-trivial _familiar_ code where typing it all would be slower than prompting the llm. Maintaining LLM context is the key here imo and stopping it when you see weird stuff. So it requires you act as thr senior partner PR:ing everyhting.
This begs the question, how many of the newer generation of developers/engineers "know what a well architected piece of code is supposed to look like"?
Llm frameworks !!