If you think restricting technology means banning all new technology, I'm not sure you read this clearly. At Redgate, we limit technology, especially in projects that often see staff turnover every year. This is to ensure that we work within a limited set of platforms, languages, etc. that everyone knows to some extent.

We allow this list to grow and change, either by adding new items or by removing old ones. There needs to be slow change in the way we write code, especially as new processes and tools prove to be better. Anyone is free to experiment, and that is encouraged. In fact, we have an F# guild looking to grow the usage of that language.

However. We do not just allow those new technologies to be used in revenue projects. We used to, and that resulted in some items being difficult to maintain.

This also applies to techniques examined in code reviews and internal packages/libraries/frameworks for building. We want to limit what's there. Not prevent new ones, and certainly ensure we can retire old ones, but to ensure that the staff can, and wants, to work with what we use.