Hacker News Reader

Comment by zby | Hacker News Reader

I believe there should be easy ways to move logic between prompts and code in a smooth ways. Moving from prompts to code is for getting deterministic, fast, well defined and cheap execution - the other way is when you want to quickly extend your system or when you want to relax a pre-condition (which is extending if you look into it deeply).

There are some inroads into this vision - but I haven't seen anything build directly for this (beside my own experiment).

I have some 'vibe noted' notes on this: https://zby.github.io/commonplace/notes/unified-calling-conv..., https://zby.github.io/commonplace/notes/rlm-tendril-and-llm-...

View on HN

The idea of morphing prompts to code and back is revolutionary.

You may want to read earlier discussions https://news.ycombinator.com/item?id=48881112 And https://news.ycombinator.com/item?id=48051562

awww for a second I thought you were maybe talking about something like this: https://news.ycombinator.com/item?id=48905887

I am not sure if this is sarcasm - but just in case - https://github.com/sshwarts/skillscript does not offer a unified namespace for functions and prompts (agents) like https://github.com/zby/llm-do (currently in suspended development). There are now also the 'dynamic workflows' in Claude Code that are pretty interesting approach - they are like a compiled prompt in many aspects.

No sarcasm. In that thread we discussed recursive, interleaved application of code and prompt. No morphing, however.

Thanks for dynamic workflow pointer. I don’t know if I like JavaScript for workflow definitions tho. IMHO sshwarts has the right idea on severely constrained workflow definition language. I plan to look closer into ADK2 workflows as well.

I’m not saying anyone did what you are doing, I’m saying multiple pieces are converging on that, at least in my imagination.

Thanks!

It is all binary, all the way down. Code is text that passes the compiler's checks. Human language is text that has a really ambiguous compiler. And all text is still binary in the computer.

If you think about it, the transformers architecture was created to solve language translation. It works well for human language to code and other way around, already!

What we need is better tooling for this translation on either side. I started working on https://github.com/brainless/nocodo/blob/feature/praxis_agen... for this reason - how can we go from human language to code representing it.

Reply on news.ycombinator.com