This is a very interesting article. I particularly like that it appreciates that things change with scale - you should implement things one way for 100 users, a

This is a very interesting article. I particularly like that it appreciates that things change with scale - you should implement things one way for 100 users, another way for 1000 users and probably again for 10000 users. That being said, things do change with time and team scale too. I am responsible for some code that is > 10 years old, and the way things are done have changed - some things down to fashion, some things down to the skills in the team and some things down to the size of the team. As such, we need to refactor and bring it up to the latest building regs.