+1

Data Culture.md

reviewed

··· 102 102 - [Bring the collaboration process inline with the assets to allow for better handoffs and feedback](https://pedram.substack.com/p/data-can-learn-from-design). 103 103 - [Culture eats strategy (and tools) for breakfast](https://news.ycombinator.com/item?id=29062266). Until there's a cultural mindset shift towards how companies value data and metadata, nothing will change. 104 104 - [Tools eat process for breakfast](https://benn.substack.com/p/the-product-is-the-process). No matter how much you blog about best practices, or how many talks you give about better ways to work, people will eventually find their way back into the behavioral grooves cut by the products they use (e.g: dbt, GitHub, ...). 105 105 + - Similar to [logical arguments](https://x.com/tayloramurphy/status/1972503102625567172), data alone doesn't always change someone's mind! 105 106 - Most of the work done in data is in an effort to **reduce entropy** — Model data to remove inaccuracies, turn commonly asked questions into self-serve reports, and funnel ad-hoc questions into a formalized request process. This kind of attitude the nature of data practitioners. In the case of driving decisions with data, **embrace the chaos**. 106 107 - Data doesn't so much drift towards entropy, **but sprints at it**. 107 108 - [Navigating the chaos to arrive at a trustworthy recommendation is one of the most important jobs to be done.](https://roundup.getdbt.com/p/iterating-on-your-data-team). Decisions usually need to be taken faster and data analyst are [not invited to the table early enough](https://petrjanda.substack.com/p/bring-data-analyst-to-the-table). Again, be lean and iterate.

+1

Programming.md

reviewed

··· 25 25 - Reuse [patterns](https://www.digitalocean.com/community/tutorials/gangs-of-four-gof-design-patterns). 26 26 - The number of moving pieces on average doubles every 18-24 months. No one fully understands [[Systems]]. 27 27 - [There are different notions of simplicity](https://vitalik.eth.limo/general/2018/11/25/central_planning.html) (Kolmogorov complexity vs VC Dimension). What is "simple" to describe or appears to have few knobs in one language for describing it is devilishly complex in another, and vice versa. 28 28 + - [Good taste is writing code that looks so simple, everyone else says "anyone could have written that!"](https://news.ycombinator.com/item?id=45411143) 28 29 - **Do one thing and do it well**. 29 30 - By focusing on a single task, a program or function can eliminate much extraneous code that often results in excess overhead, unnecessary complexity, and a lack of flexibility. [Good software makes hard things easy](https://medium.com/s/story/notes-to-myself-on-software-engineering-c890f16f4e4d). 30 31 - Design composable primitives. Name things simply and clearly.