b-luu

4 ms·

1. 1.▲
   by b-luu 4y ago

   Thanks for your suggestion. I have nothing against dimensional modeling per-say, just the uptime effort (and initial feedback lag) that it generally brings with it in the beginning. Another issue I've observed with teams trying to form
2. 2.▲
   by b-luu 4y ago

   Thanks for sharing!! Author here: yeah I ended up insisting a bit much on dbt as a basis although the method I'm describing in the article can definitely be applied to any kind of modeling framework (or lack of) Anyway, please let me k
3. 3.▲
   by b-luu 4y ago

   Good points, but a bit extremist. I definitely agree with the over-hype making simple mundane tasks way harder than they should be. So yeah, do NOT over-engineer!! But, on the other hand, doing everything with a single Postgres and spreadsh
4. 4.▲
   by b-luu 4y ago

   Meh, depends on the data teams (and their chosen suite of tools)... Or on the Excel users Both sides can either hack together horrible work-arounds (a matter of "when you have a hammer, everything looks like a nail...") as well as
5. 5.▲
   by b-luu 5y ago

   Author here. Any feedback welcome ^^ Thanks for posting mooreds !
6. 6.▲
   by b-luu 6y ago

   As mentioned by cgardens in reply to another question, you can read through John's (one of the founders of Airbyte) article on the future of ETL/ELT: https://airbyte.io/articles/data-engineering-thoughts/