stuff
This commit is contained in:
parent
170e50c30c
commit
97d27ac539
2 changed files with 180 additions and 2 deletions
|
|
@ -16,6 +16,11 @@ Some notes and thoughts after my first week.
|
|||
- Does it need to be multiple engines? Is it worth it? Can we do it? What are the risks of sticking to only one?
|
||||
- Why not another postgres instance in the `lana` deployment?
|
||||
|
||||
## Coupling with database
|
||||
|
||||
- Should the database stay public to the data downstream dependants?
|
||||
- Or do we want to introduce an additional layer for decoupling and stable interface?
|
||||
|
||||
## Visualization layer
|
||||
|
||||
- Do we want to bring a batteries included approach to visualizing data about the bank? Should that be a responsibility of the app UI, or of an additional reporting solution? Or embbeding reporting within the app?
|
||||
|
|
@ -25,8 +30,7 @@ Some notes and thoughts after my first week.
|
|||
- data contracts
|
||||
- dbt unit testing
|
||||
- data integration testing
|
||||
- more solid development data?
|
||||
|
||||
- more solid development practices in data?
|
||||
|
||||
## If you asked meTM
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue