There are many good nuggets of content in the piece, but at its core is an artifact referred to as the Cultural Manifesto: “a document or a set of materials to help your entire engineering team get on the same page about how you make and operate things, and how you function as a team”.
Not surprisingly, it has three main sections covering the organization concrete, documented opinions in three main areas:
- How we make things – code reviews, branching, deploying code, enabling features, etc.
- How we operate things – monitoring & alerting, production access, data integrity, etc.
- How we function as a team – role of engineering, culture and values, conflict resolution, etc.
It’s a phenomenal starting-point checklist to go through. If you don’t have a concrete, documented opinion on one of these line items – you probably should.
“Don’t let your CFO start capitalizing R&D labor” is my own personal favorite 🙂