DevSecOps Engineer, Author, and Mentor

Additional patterns that support the same values

The three ideas I mentioned are the core of what I would recommend. There are also several supporting patterns that reinforce the same values.

Use bounded collaboration windows

Pairing, mobbing, and shared working sessions can be excellent tools when they are bounded, purposeful, and chosen for the kind of work at hand.

There are situations where intense synchronous collaboration is exactly the right tool:

• onboarding
• incident response
• shared debugging
• risky migrations
• hard architectural knots
• knowledge transfer in fragile areas of the codebase
• moments when a team genuinely needs to think together in real time

The problem begins when the tool becomes the atmosphere.

Read More

What Better Collaboration Looks Like in Practice

In the first two parts of this series, I argued that some collaboration models carry costs their advocates rarely name clearly enough. On the human side, continuous managed availability can create chronic vigilance, bodily constraint, public diminishment, flattened expertise, and a workday in which a person is never fully allowed to settle into the problem. On the business side, the same model can reduce deep-work capacity, increase transition cost, misallocate senior talent, create shallow understanding, inflate ceremony cost, and quietly lower the return an organization gets from expensive technical labor.

That would be enough reason to reject the worst versions of the model.

It is not enough on its own.

Read More

Misallocated talent is a business problem

This point deserves to be stated plainly: flattening distinct engineers into generic units of "senior technical labor" is commercially irrational, not just dehumanizing.

Highly experienced people are costly for a reason. They are not merely faster typists or more expensive implementers. They bring judgment. They see risk earlier. They recognize patterns. They know when a local decision will create downstream drag. They often prevent damage that never becomes visible because their presence kept it from happening.

When an organization deploys those people as if they were interchangeable bricks, it wastes precisely what it is paying for.

Read More