“… found it extremely difficult dealing with bug fixes and feature requests relating to the other developer's code, who used a substantially different coding style. In the end we had to rewrite all our plugins for Construct 3, and so we ended up rewriting all the code anyway, which was particularly challenging given we hadn't written it ourselves in the first place and didn't have a deep understanding of how it worked. It's far easier now it's all our own code.”

I love this article and agree with almost all of it. However, this portion I find to be guilty of elitist programming mantra.

The bottom line is when you’re dealing with large code bases, there will be different coding styles present and the likelihood of everyone agreeing on a single coding style is virtually nil. Insistence on coding purity is an issue that can erode camaraderie in a team and develop into petty political in-fighting. Handling this problem in a tactful way is one of the keys to success in large code bases, as developers have their own styles and draconian insistence upon a single style can limit the talent that’s willing to work with you and your team.