👋 Hi everyone! We're brand new to Hamilton, but already huge fans of its concepts ✨ We're migrating over from DVC (which was great for starting out), but today we are ready to free ourselves from the YAML jungle! 🌴🌴 Our main open question right now is around debugging and Developer Experience (DevEx). Coming from DVC, we are used to having atomic scripts with local input/output files readily at hand. We're curious about how to maintain a great DevEx within a functional, all-in-memory context. • How do you typically debug a long DAG? • How do you isolate specific steps during development or when something fails? Any tips, workflows, or remarks are highly welcome!

Welcome! Perhaps the AI SKILLs might be a useful place to start, though it's not exactly what you asked. See hamilton/.claude-plugin/skills/hamilton-dev-workflow at main · apache/hamilton Of course if the existing SKILLs are not enough - contributions are always welcome!

@engineering welcome. Hamilton was designed to make it really easy to unit test and test any sequence within a DAG. I would look up the .execute() function on the driver. In combination with outputs, and overrides you can easily control what gets where. You can also try the local UI and tracker to inspect the output of a run.