4 ms·

My agents often write themselves scripts. Isn't that effectively what you're asking for? Prompting for scripts can also be a useful time and accuracy tactic whe

My agents often write themselves scripts. Isn't that effectively what you're asking for? Prompting for scripts can also be a useful time and accuracy tactic when you know it'll be a good fit for it.

sisve 5mo ago
Yeah, the problem is that I do not think the agents is good at reusing scripts and stitching it together.At least for me it's recreating to much similar. I hope we will see platforms like windmill.dev find the optimal solution for this. I have not been able to test it enough. But have a platform that gives you some observability out of the box and protect secrets from llm is nice
- reddit_clone 5mo ago
  I noticed that too. Unless you _ask_ for a script, they throw away the scripts they write. They are particularly bad at complex multiline parsing. Writing all sorts of weird/crude python/awk scripts and getting confused in the process. I wish they would use Perl6/Grammer or Haskell/Parsec or similar and write better parsing scripts.
  - quinnjh 5mo ago
    For the non haskell folks like myself, what would that look like/ why is parsing better? Perl i get
    - reddit_clone 5mo ago
      Perl has powerful regular expressions, but it only goes so far. Doing multiline/nested structured parsing is too painful. Perl6/Raku has built in grammers that can do that idiomatically. If you have a couple minutes, give this a glance. It will give you an idea. https://andrewshitov.com/2018/10/31/a-simple-parser-in-perl-6-grammars/ https://andrewshitov.com/2018/10/31/a-simple-parser-in-perl-... I am no expert in haskell either. But parsec is similar in concept.
falkensmaize 5mo ago
The problem is that code it spits out on the fly is untested and untrustworthy. Identify the parts of your workflow that could be accomplished with regular code - write and unit test that code, with LLM help if you want, and use the llm as the orchestrator only.

My agents often write themselves scripts. Isn't that effectively what you're asking for? Prompting for scripts can also be a useful time and accuracy tactic when you know it'll be a good fit for it.

sisve 5mo ago

Yeah, the problem is that I do not think the agents is good at reusing scripts and stitching it together.At least for me it's recreating to much similar. I hope we will see platforms like windmill.dev find the optimal solution for this. I have not been able to test it enough. But have a platform that gives you some observability out of the box and protect secrets from llm is nice

reddit_clone 5mo ago
I noticed that too. Unless you _ask_ for a script, they throw away the scripts they write. They are particularly bad at complex multiline parsing. Writing all sorts of weird/crude python/awk scripts and getting confused in the process. I wish they would use Perl6/Grammer or Haskell/Parsec or similar and write better parsing scripts.
- quinnjh 5mo ago
  For the non haskell folks like myself, what would that look like/ why is parsing better? Perl i get
  - reddit_clone 5mo ago
    Perl has powerful regular expressions, but it only goes so far. Doing multiline/nested structured parsing is too painful. Perl6/Raku has built in grammers that can do that idiomatically. If you have a couple minutes, give this a glance. It will give you an idea. https://andrewshitov.com/2018/10/31/a-simple-parser-in-perl-6-grammars/ https://andrewshitov.com/2018/10/31/a-simple-parser-in-perl-... I am no expert in haskell either. But parsec is similar in concept.

falkensmaize 5mo ago

The problem is that code it spits out on the fly is untested and untrustworthy. Identify the parts of your workflow that could be accomplished with regular code - write and unit test that code, with LLM help if you want, and use the llm as the orchestrator only.