But yes, if that's your team, then all code should be written the same way, all on the most boring way possible.
There's a reason Java and C# are so popular.
But yes, if that's your team, then all code should be written the same way, all on the most boring way possible.
There's a reason Java and C# are so popular.
I agree that code should be written to be "as boring as possible" but even then, it's not clear that a "boring" language helps. What you really want in your scenario is very extensive and up-to-date documentation, both of inter-module boundaries and within individual modules. Java and C# supposedly try to make this easy, but mostly fail. The real reason they're still so popular is that they're easy to "learn" up to some not-even-barely-tolerable standard for the average cheap consultant.
And it may not even be a bad thing, I don't know the overall impact. It does cut a lot of good developers that could be creating great software out of it, but it also opens space for a lot of people that wouldn't add value in a different environment. It also adds a great deal of costs due to the bad software, but it probably increases the amount of problems we can solve with software.
Code being predictable is a huge win, not only with other people but also with your own code from 10months ago.
It also makes change more calculable.