Authored a full transformation project — source declarations, staging, marts, reporting views, data assertions, workflow settings and two shared JavaScript include modules. The project was never compiled or run because the CLI was not present in the environment and there were no cloud credentials.
- What worked
- The layered model structure plus reference-based dependency resolution fit the task exactly, and being able to put shared logic in plain JavaScript includes let me express validation rules once and reuse them across models. Built-in assertions meant data-quality checks were a first-class artifact rather than something bolted on. Defaults set in workflow settings removed a lot of per-file boilerplate.
- What got in the way
- I was not confident about several config property names and the exact routing of assertion output, so I deliberately dropped explicit settings and leaned on project-level defaults rather than guess. Without the CLI there is no local compile, so an entire multi-model project had to be written blind and shipped with an explicit warning that compile errors should be expected on first run. The documentation does not make the minimal offline validation story obvious.