skrawcz commented on issue #556: URL: https://github.com/apache/burr/issues/556#issuecomment-3017354451
@mecampbellsoup thanks for the issue. Yeah we don't have anything like that written up yet! Would you like to contribute? Short story for Burr is that: 1. It's the only Apache governed project -- so you can invest and become part of the company and help drive direction, versus being beholden to VC dollars pushing growth and then at some point monetization... 2. To my knowledge, the Burr UI is the only Open Source UI that builds specific observability tooling to help you observe and inspect both LLMs and state. 3. Burr's design philosophy is to ensure that productionization isnt' going to be painful with customization (e.g. langraph forces you to bring in langchain for any customization) and not getting in the way of future iteration is what we focus on (see [this blog](https://blog.dagworks.io/p/the-graduation-problem-avoid-frameworks)) -- e.g. this manifests as you have to bring the LLM calls, Burr does not do that on your behalf, so you _always_ can know what the prompt is that you sent to the LLM because it's up to you to control; we think that's ultimately the best thing to do. > User sends a message to our assistant > We attempt to classify (via LLM call) their message and assign a "conversation type" > If the user's message is classified with at least 1 category/type, and the LLM reports a confidence of at least 90%, we proceed to another flow that we call "extraction" whereby we extract semantic information from the user's text, and ask follow up questions for anything we are missing to be able to answer their question for the given conversation type. > If the user's message is NOT classified, or the classification confidence score is < 90%, we want our bot to ask the user to clarify or expound upon their initial message. What I counsel people on is to do a bake off. Write this code vanilla -- frameworks should really just be syntactic sugar over vanilla options. Be sure to include observability and logging concerns in your bake-off, since POC code doesn't look like production code without it. It might very well be that you haven't graduated to a complex enough problem if all that you have is some if else statements ... Does that help any? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
