This, combined with contracts, could make a lot of things so much fun now!
For those who don't know (which is probably everyone but me), I ported the design-by-contract pattern in Python and combined it with LLMs. This was early 2025. I originally wrote about it here: <a href="https://leoveanu.com/2025-03-01-dbc/" rel="nofollow">https://leoveanu.com/2025-03-01-dbc/
. Contracts are a core feature of SymbolicAI ever since. The community seems to have loved it too (<a href="https://news.ycombinator.com/item?id=44399234">https://news.ycombinator.com/item?id=44399234).
I think I'm starting to glimpse the implications and it's gonna change agentic workloads if it holds up to scrutiny. It's too early for me to tell anything other than jot down some rough thoughts.
In short, you get blazingly fast semantic branching you can use in control flows. For contracts, I can now directly take the data model that you have to design and convert it into Jev's expected format. Or I can use Jev for semantic branching in postconditions.
If my understanding is correct, that should be doable, but I need to think more about it. It could be that with Jev I can finally “compile contracts” and better chain them into workflows, which is something I always wanted but didn't know how to do properly.
GP's first sentence isn't arrogant (at worst displaying a bit of false humility) because it's saying everyone but him doesn't know about a thing he did. Your second quote you apparently mis-parsed because of a minor English error (he should have said "to Python" rather than "in Python"), but to me it was pretty clear what he meant.
futurisold · · focus · HN ↗
For those who don't know (which is probably everyone but me), I ported the design-by-contract pattern in Python and combined it with LLMs. This was early 2025. I originally wrote about it here: <a href="https://leoveanu.com/2025-03-01-dbc/" rel="nofollow">https://leoveanu.com/2025-03-01-dbc/ . Contracts are a core feature of SymbolicAI ever since. The community seems to have loved it too (<a href="https://news.ycombinator.com/item?id=44399234">https://news.ycombinator.com/item?id=44399234).
I think I'm starting to glimpse the implications and it's gonna change agentic workloads if it holds up to scrutiny. It's too early for me to tell anything other than jot down some rough thoughts.
In short, you get blazingly fast semantic branching you can use in control flows. For contracts, I can now directly take the data model that you have to design and convert it into Jev's expected format. Or I can use Jev for semantic branching in postconditions.
If my understanding is correct, that should be doable, but I need to think more about it. It could be that with Jev I can finally “compile contracts” and better chain them into workflows, which is something I always wanted but didn't know how to do properly.
Eager to test. On the waiting list.
AdieuToLogic · · focus · HN ↗
[dead]
jbotz · · focus · HN ↗
GP's first sentence isn't arrogant (at worst displaying a bit of false humility) because it's saying everyone but him doesn't know about a thing he did. Your second quote you apparently mis-parsed because of a minor English error (he should have said "to Python" rather than "in Python"), but to me it was pretty clear what he meant.
AdieuToLogic · · focus · HN ↗
Not often, but yeah... I did on this occasion.
[deleted] · · focus · HN ↗
[deleted]