Why senior developers fail to communicate their expertise

Ah, now, here’s our second loop. People paying for a service.

Because once you have customers, both loops are running simultaneously. A business needs to both explore possibilities and serve customers at the same time.

But why does this lead to communication failure?

So, if the first loop’s goal was uncertainty reduction, the second loop’s goal is complexity management.

It makes a system less understandable, less debuggable, less fixable, less teachable, and ultimately, less stable.

And what risks all of that?

Senior developers worry about stability because they take responsibility for the business to continue serving customers.

Keep things working, keep things understandable, keep things debuggable, keep things fixable, keep things teachable, keep things stable.

This loop is where a lot of senior developers find themselves in. The main goal in this loop is the continuation and guarantee of service.

Depending on which loop you spend your time on, your problem is framed differently (which is why I think developers get split in their opinions on AI; some work more on one loop than the other)

... continue reading