Skip to content
~/sph.sh

psychological-safety

7 posts

psychological-safety
Who Owns This Code Now: Accountability vs Blame

Stop asking who wrote the legacy code. Separate responsibility, accountability, and blame, and make inherited code owned rather than orphaned.

engineering-culture · leadership · team-management +3

Blameless Postmortems: A Model and a Copy-Paste Template

A blameless postmortem model that fixes the system instead of finding a culprit, with a copy-paste template and where individual accountability still applies.

engineering-culture · incident-response · psychological-safety +4

Salary, Impact, or Satisfaction? The Vocation Question Every Engineer Faces

Why the salary-vs-impact-vs-satisfaction debate is a false trichotomy, and what your answer reveals about your vocational development stage.

career · team-dynamics · developer-experience +1

Working with Difficult Coworkers in Software Teams: Beyond Textbook Solutions

A field guide to engineering-specific difficult coworkers, from code-review blockers to ghost colleagues, with practical strategies that work for each archetype.

leadership · team-management · best-practices +5

Team Conflict Resolution: A Field Guide to Turning Dysfunction into High Performance

A field guide to spotting, managing, and resolving conflict in software teams, with practical frameworks and early-warning systems that turn friction into performance.

leadership · team-management · best-practices +4

Code Review Culture: From Nitpicking to Knowledge Sharing

How to transform code reviews from fault-finding into mentorship and learning opportunities that build psychological safety while improving code quality.

code-review · organizational-culture · mentorship +5

Lewis Deep Democracy in Engineering Teams: Beyond False Consensus

How Arnold Mindell's Deep Democracy principles transform technical decision-making, build psychological safety, and ensure every voice strengthens architecture.

psychological-safety · team-management · team-dynamics +4