// Topics / Culture
Culture
Definition
Culture coverage in this archive spans 6 posts from Mar 2016 to Dec 2022 and is treated as an operating model question: decision rights, feedback loops, and execution clarity. The strongest adjacent threads are leadership, engineering, and teams. Recurring title motifs include teams, security, engineering, and culture.
Key claims
- A repeated argument is that small teams ship faster when ownership boundaries are explicit.
- Early posts lean on culture and engineering, while newer posts lean on security and teams as constraints shifted.
- This topic repeatedly intersects with leadership, engineering, and teams, so design choices here rarely stand alone.
Practical checklist
- Write down ownership, escalation routes, and meeting defaults before scaling team surface area.
- Start with the newest post to calibrate current constraints, then backtrack to older entries for first principles.
- When boundary questions appear, cross-read leadership and engineering before committing implementation details.
Failure modes
- Using process to compensate for unclear ownership and weak technical direction.
- Adding management layers before tightening decision loops and execution signals.
- Applying guidance from 2016 to 2022 without revisiting assumptions as context changed.
Suggested reading path
- Start here (current state): Resilient Teams Are Boring Teams
- Then read (operating middle): Building Effective Engineering Teams
- Finish with (foundational context): Building a DevOps Culture from Scratch
Related posts
- Resilient Teams Are Boring Teams
- Embracing Remote Work: Benefits, Dangers, and Overcoming Challenges
- Your Startup Doesn’t Need a Security Team. It Needs a Security Champion.
- Building Effective Engineering Teams
- Building a Security-First Engineering Culture
- Building a DevOps Culture from Scratch
References
6 entries tagged “Culture”