← Back to Issue

Make No Assumptions

From Pointer · subscribed via aiste.ulozaite@gmail.com · original ↗ · unsubscribe

When that architect leaves, they are replaced by someone who aspires to operate in the same code layer, but simply cannot because they lack enough context to do so. As a result, that new replacement creates a new code layer, despite not intending to. If the team runs through a handful of folks as the new team leads struggle, it’s easy to end up with a complex code horizon very quickly.

Couldn’t fetch the full article — read it on the original site ↗.