
elijah
2.7K posts

elijah
@elijahbenizzy
Ex-Two Sigma, ex-Trello, ex-Stitch Fix. Building DAGWorks, Inc. (YC W23)


Super excited for this HOW-TO on running the Hamilton UI on @SnowflakeDB : "Observability of Python Code and Application Logic with @hamilton_os UI on @SnowflakeDB Containers" Services by Greg Przemyslaw Kantyka link.medium.com/FIwGhJqzsPb



A @burr_framework user shared this video youtube.com/watch?v=evmZTh… with me on the "problem with frameworks". Worth a watch. I 💯% agree with the take home. The "coupling problem" is the reason why people graduate out of frameworks like @langchain & @llama_index. You become overly coupled and then find yourself overtime asking why am I using this? It's not that the framework authors did this maliciously, it's just that they optimized for their needs, in this case for POCs, which is not the same as long lived maintainable code. That's why we see people either build their own frameworks, or they hopefully discover @hamilton_os & @burr_framework and realize that there are frameworks that allow "loose coupling" that don't get in your way (as a platform person and framework author we optimize for maintainable code). A good example of this is @FastAPI - very easy to not couple your business logic and iterate quickly no matter the age of the code. So how can you tell where a framework lies on the spectrum of tight coupling versus not? Some tests: (1) How many "objects" do I need to use from the framework to couple the logic I want to happen? The fewer the better. E.g. with @hamilton_os by default it's 0. With @burr_framework it's just 1 and that's due to state for edge transitions, but that's easy to decouple from. (2) How many framework imports do you need to get something to run? The less the better - consider @burr_framework vs @langchain using #langgraph (see images) If you're feeling framework pains, or are curious on how it can be done right, checkout: github.com/DAGWorks-Inc/b… (agents) github.com/DAGWorks-Inc/h… (pipelines/tools) or subscribe to our blog - blog.dagworks.io #python #opensource #genai #llmops
















Guess who is on the #instructor blog? ME! The TLDR: - Use #burr and #instructor to ship more quickly - Instructor for structuring LLM interactions - Burr for app structure & observability In this example we create flashcards from @YouTube videos. #flashcard-generator-with-instructor-burr" target="_blank" rel="nofollow noopener">python.useinstructor.com/blog/#flashcar…

🎉 Excited to announce that @sh_reya has joined us @DagWorks as an advisor. Her research & what we're building with @hamilton_os & @burr_framework overlaps. I'm excited to work together more closely. For more see my update: new features, docs, video etc linkedin.com/pulse/week-oct…

Check out ep. 22 of Generationship! Elijah Ben Izzy (@elijahbenizzy) of @DagWorks unpacks his work with AI tools, the importance of user engagement in chatbot responses, and the future of AI in the context of energy consumption and hype. hubs.ly/Q02TC_P80





