A reflection on knowledge silos in engineering teams: why they often start as responsibility rather than ego, and what helps spread context before one person becomes the queue.
The second part of a series on engineering effectiveness anti-patterns, focused on what happens when we keep postponing system health in favor of short-term feature delivery.
The first part of a series on engineering effectiveness anti-patterns, focused on how constant context switching quietly erodes focus, depth, and overall effectiveness in day-to-day engineering work.
A reflection on territorial behavior in engineering teams: why it shows up, why it hurts collaboration, and how to catch it in yourself before it damages trust.
Listening to Boris Cherny talk about “coding being largely solved” felt familiar — it describes a shift many of us are already living, even if we don’t always name it.