+2

Data/Analytics Engineering.md

reviewed

··· 2 2 3 3 - Analytics Engineering is the organization of an organization's information. 4 4 - [Real impact comes from continuous decision-making and implementing actions with feedback](https://news.ycombinator.com/item?id=22808006). 5 5 + - [More analysis might not be the best solution if you can't validate or take actions on previous analysis](https://twitter.com/ejames_c/status/1753692862548697464)! 5 6 - Accept that [analytics is a mess](https://benn.substack.com/p/analytics-is-a-mess). 6 7 - Explicitly create separate workspaces for curated (production) and messy (experimental) work. 7 8 - Reports are rarely read, and often forgotten. [[Data Culture|Decision-making involves getting data, summarizing and predicting ad then taking action]]. ··· 50 51 - [MetricsDAO](https://github.com/MetricsDAO) 51 52 - [RA Analytics](https://github.com/rittmananalytics/ra_data_warehouse) 52 53 - [Anomstack](https://github.com/andrewm4894/anomstack) 54 54 + - [Skrimmage](https://github.com/Skrimmage/Data-Platform) 53 55 54 56 #### Dagster Resources 55 57

+1

Teamwork.md

reviewed

··· 6 6 - Stick to defining components and keep concepts generic (cache, [[databases]], algorithm, ...). Show how the components interact. 7 7 - Define boundaries and limitations of each component. 8 8 - Work in the open and [[Documentation|document]] everything. Transparency increases understanding and reduces synchronization challenges. **[Emulate Open Source projects](https://tomayko.com/blog/2012/adopt-an-open-source-process-constraints) and [[Remote Jobs|remote companies]]**. 9 9 + - [Write weekly updates](https://doingweeknotes.com/) and share them in a common place. 9 10 - To make everyone more productive and happy: **Make feedback loops fast**. [Some best practices](https://simonwillison.net/2022/Oct/1/software-engineering-practices/): 10 11 - Tested, automated process for new development environments. 11 12 - Automated preview environments.