3 ms·

>the whole article assumes the only language in the world is Python. This was my take as well. My company recently started using Dspy, but you know what? We h

>the whole article assumes the only language in the world is Python. This was my take as well. My company recently started using Dspy, but you know what? We had to stand up an entire new repo in Python for it, because the vast majority of our code is not Python.

sbpayne 6mo ago
I think this is an important point! I am actually a big fan of doing what works in the language(s) you're already using. For example: I don't use Dspy at work! And I'm working in a primarily dotnet stack, so we definitely don't use Dspy... But still, I see the same patterns seeping through that I think are important to understand. And then there's a question of "how do we implement these patterns idiomatically and ergonomically in our codebase/langugage?"
- redwood 6mo ago
  Out of curiosity, what are you finding success with in dotnet land? My observation is that it's not clear when Semantic Kernel is recommended versus one of multiple other MSFT newly-branded creations
  - sbpayne 6mo ago
    we have been using Agent Framework. I also have been eyeing LlmTornado. Personally, I find dotnet as a whole hard to implement the kind of abstractions I want to have to make it ergonomic to implement AI stuff. I've been fiddling around with many prototypes to try to figure out the right way to do this, but it feels challenging; I'm not yet familiar enough with how to do this ergonomically and idiomatically in dotnet haha
  - CharlieDigital 6mo ago
    Agent Framework + middleware + source generation is the way to go. Agent Framework made middleware much easier to work with. Source generation makes it possible to build "strongly typed prompts"[0] Middleware makes it possible to substitute those at runtime if necessary. [0] https://github.com/CharlieDigital/SKPromptGenerator/tree/main https://github.com/CharlieDigital/SKPromptGenerator/tree/mai...
BoorishBears 6mo ago
Why did you do that instead of using Liquid templates?

sbpayne 6mo ago

I think this is an important point! I am actually a big fan of doing what works in the language(s) you're already using. For example: I don't use Dspy at work! And I'm working in a primarily dotnet stack, so we definitely don't use Dspy... But still, I see the same patterns seeping through that I think are important to understand. And then there's a question of "how do we implement these patterns idiomatically and ergonomically in our codebase/langugage?"

redwood 6mo ago
Out of curiosity, what are you finding success with in dotnet land? My observation is that it's not clear when Semantic Kernel is recommended versus one of multiple other MSFT newly-branded creations
- sbpayne 6mo ago
  we have been using Agent Framework. I also have been eyeing LlmTornado. Personally, I find dotnet as a whole hard to implement the kind of abstractions I want to have to make it ergonomic to implement AI stuff. I've been fiddling around with many prototypes to try to figure out the right way to do this, but it feels challenging; I'm not yet familiar enough with how to do this ergonomically and idiomatically in dotnet haha
- CharlieDigital 6mo ago
  Agent Framework + middleware + source generation is the way to go. Agent Framework made middleware much easier to work with. Source generation makes it possible to build "strongly typed prompts"[0] Middleware makes it possible to substitute those at runtime if necessary. [0] https://github.com/CharlieDigital/SKPromptGenerator/tree/main https://github.com/CharlieDigital/SKPromptGenerator/tree/mai...

BoorishBears 6mo ago

Why did you do that instead of using Liquid templates?