Hi everyone, I just wanted to know if there were any best practices recommanded for the project organization ? For example, in the project https://github.com/dagster-io/quickstart-etl , there is only one folder quickstart-etl where all the code (jobs/assets) is put inside. Do you recommand splititng all our assets in different folders depending on : team usage / data source type / business model use-cases ?

Hi Charles. I recommend putting all assets inside one folder (you can have nested levels inside that organize by team etc.) so you can use functions such as

load_assets_from_package_module

. Would also recommend that assets that depend on one another live in the same file or directory, to keep dependency management easier.

Thanks for your insights ! Alright we'll keep everything is the same folder and use naming convention to "sort"/"arrange" them.