So did I misread the article or..?
So did I misread the article, or are they actually dropping direct use of SQL in favor of letting their customers use this (formerly seperate) dbt software for free which *also* supports SQL?
I mean, I agree, "don't mess with things", but if it's a matter of being able to keep using SQL, just using it through dbt rather than directly, then it seems like it's not really a problem. Of course it could be like two very different SQL dialects, and the management decided "it's SQL" and it's close enough -- THAT could be a PITA for sure.
Biting the hand that feeds IT
