i cannot type "make me an exploit based on whatever these diffs fixed" into a compiler and get usable output. and i cannot type "make me a budget, here is 6 months of credit card receipts" into a compiler and get a budget. etc.
This sentence from the article really stuck out to me.
> and you write the rule down so clearly that nobody (human or otherwise) has to guess again.
Writing rules, or steps, unambiguously in a high level language and having those statements translated to lower level languages, that ultimately get executed by a machine, is what compilers do.
The commands you gave were not unambiguous at all and although an LLM would produce a result, the result would definitely be nonsense.
"make me a budget, here is 6 months of credit card receipts"
For example, a valid budget requires some knowledge of expected income...
i forgot my golden rule of never giving examples or using analogies while on HN because people hyper focus on nitpicking the specifics of the example/analogy rather than the overall point being made.
amend my example to "make me a budget, here is 6 months of credit card receipts, and i make somewhere around $60k per year".
Yes, this is a real problem. It is also directly against the guidelines.
And it definitely is not what LLMs do, even if you pepper your rules with “NEVER, ever deviate from these rules”.
Here are some suggestions,
Workato, Boomi, Sitecore AI, Optimizely Opal, Workfront AI...
You will naturally have to split the budget calculation in a few agentic nodes, and maybe a couple of tools.
i thought we were talking about compilers vs. llms.
Agentic programming tools are nothing other than the old ideas from UML code generation in a new package.
Not sure I agree with that. That was still a transformation of sorts.
Better accept that in a few more model iterations, the code being generated is a matter of changing a markdown file.