this repo has no description
:memo:
+1
-1
+1
-1
Data/Analytics Engineering.md
+1
-1
Data/Analytics Engineering.md
···
21
21
- [[Teamwork | Collaborate with your team]] and break down complex models into reusable pieces.
22
22
- Working with data is like exploring the horizon. It changes as soon as you look it from a higher place (more data).
23
23
- Reduce the areas where business logic can be injected, create “time to live” policies on last mile transforms, build a culture of standardizing + celebrating access to cross-functional codebases.
24
-
- People default to writing business logic in the tool they are most comfortable with. The best way for data teams to prevent sprawling business logic is not just to limit last mile transforms in other tools, but also to invite others into their tools.
24
+
- People default to writing business logic in the tool they are most comfortable with. The best way for data teams to prevent sprawling business logic is not just to limit last mile transforms in other tools, but also to invite others into their tools. [This logic will be written, and if the data team gatekeeps, it will be written outside of their visibility](https://ian-macomber.medium.com/data-systems-tend-towards-production-be5a86f65561). If a data team can educate and encourage contributions to their codebase, they invite code to be written where it most belongs.
25
25
26
26
27
27
## Resources