Elektrine lite

← Feed

@jonocarroll@fosstodon.org

2026-05-04 22:59 UTC

@noamross @defuneste @tylermorganwall this is one of the points I was trying to make in the Analysis section - I think dbt's scope ends there and expects an analyst to pick up the 'analysis ready' data in a separate project. {targets} can combine all the steps and keep building, but with the trade-off of maybe taking on too much responsibility. Hence my question of 'what is too big?'

Replies (2)

  • @defuneste@fosstodon.org 2026-05-04 23:04

    @jonocarroll @noamross @tylermorganwall 💯 I definitely did stuff with targets that were bordeline using PG has back end and using time stamp and/or number or row return for targets to keep track. I think the test set podcast make a good case of explaining why it make sense in a corporate setting: SQL people, need of contract between team, etc (but fail to see that targets was here :P)

    Open ##2044475

  • @defuneste@fosstodon.org 2026-05-04 23:22

    @jonocarroll @noamross @tylermorganwall Now that I think also, I would say that for the user dbt is "independent": you just need to learn the framework. {targets} is less opinionated and rely on other parts of the R ecosystem. I am still using it inside an R package (and always unsure if that is "right"), use testthat for unit tests (but also to do some "data structure" check) and rely also on R package for documentation... It would be beneficial to "framework" it a bit.

    Open ##2044476