One risk of low-code is that it alienates engineers. When you build dashboards in code, you're an engineer. When you build dashboards in Tableau, you're a "dashboard builder." No engineer wants to be a dashboard builder. You'll get a different audience (which is fine, the dbt equivalent of "dashboard builders"), and they won't be engineers. Engineers take pride in writing code, nothing more and nothing less.
The goal is explicitly to bring new folks into the tent :) Nothing about this functionality detracts from existing experiences--CLI, IDE, etc.--and I certainly don't expect that data engineers / analytics engineers are going to use the low code experience as their dominant modality.
As long as it writes code better than Dreamweaver wrote HTML/CSS you should be fine ;-) I get the idea you are going for I think - I first learned to program visual basic by recording Excel macros and looking at the code. The key is to be able to move back and forth seamlessly -- something Macromedia spectacularly failed at. best of luck!
Really happy about the new bigger/broader vision! I think most of us are tired of the tool sprawl and ready to consolidate!
One risk of low-code is that it alienates engineers. When you build dashboards in code, you're an engineer. When you build dashboards in Tableau, you're a "dashboard builder." No engineer wants to be a dashboard builder. You'll get a different audience (which is fine, the dbt equivalent of "dashboard builders"), and they won't be engineers. Engineers take pride in writing code, nothing more and nothing less.
The goal is explicitly to bring new folks into the tent :) Nothing about this functionality detracts from existing experiences--CLI, IDE, etc.--and I certainly don't expect that data engineers / analytics engineers are going to use the low code experience as their dominant modality.
As long as it writes code better than Dreamweaver wrote HTML/CSS you should be fine ;-) I get the idea you are going for I think - I first learned to program visual basic by recording Excel macros and looking at the code. The key is to be able to move back and forth seamlessly -- something Macromedia spectacularly failed at. best of luck!