+1

Automation.md

reviewed

··· 10 10 3. Create automation. Create a script that runs everything. 11 11 - Drive standards through automation and building internal tools/scripts rather than through extensive [[documentation]]. 12 12 - Standards can help to reduce this friction but take time. Before jumping into standards processes, [consider other ways to encourage consistency](https://blog.ldodds.com/2023/09/18/consistency-before-standards/). 13 13 + - If you jump into standards, [make them open, modular, interoperable, customizable and, extensible](https://voltrondata.com/codex/standards-over-silos#1-3-5-composable-systems-are-MICE). 13 14 - Makefiles are a great way to document and consolidate different projects of a team. Each project should have a `make` that runs it, and perhaps a `make deploy` to deploy it. Language and tool independent!

+1

Teamwork.md

reviewed

··· 28 28 - You can also have no durable cross-functional teams. Teams assemble around a project and disperse once the project is done. 29 29 - Run [Automated Check-ins](https://basecamp.com/features/checkins) to share things explicitly. What are people working on, what are they planning to work on next, ... 30 30 - The right way to promote people is to give them [meaningful and clear goals](https://youtu.be/oIMvMb5wVO4) for the organization and promote them if they hit the goals. 31 31 + - [If you don't promote and communicate your work, no one else will](https://twitter.com/natolambert/status/1709598547178582373). 31 32 - Lack of ownership is the root of all evil. 32 33 - Having skin in the game improves the decision making process. 33 34 - [Have direct responsible individuals for everything. Everyone's problem is no one's problem](https://nintil.com/programming). Having a name accountable instead of a vague "the team" or "the process" makes it easy to make changes.