[elthor89]

Good article, sometimes a bit hard to read with all the links to other blog posts.

However there are some good nuggets in this article like this one: "That’s when I realized: we’d built a dependency on one person’s specialized knowledge. And that knowledge had nothing to do with our actual product."

I see that at more smaller orgs, where they want to have technology X but fail to realize it requires a small team. Not because its a 3 man job to operate but because if 1 leaves or is unavailable the knowledge is gone. The knowledge can be acquired but it takes some time, and that in between period can be painful. When you tell them that and then they start to calculate the costs, it can be sobering.

The advice to keep the tech boring and widely embedded in the organization is something I agree with.