I think you need to re-read the article, try to get past the allegorical beginning. The author is a software developer like you and me.

If you've worked with a team to build software, you know that everyone's got their own ideas or someone wants to use the hottest new tool or programming language of the day. If nobody is careful, then after awhile the team might have a really confusing tech stack with major parts in totally different implementations, even if that didn't happen, everyone's got their own preferred approaches for organizing code, etc. It's always turning into a hodgepodge if there's no discipline.