Jun 27, 2019
Most organizations today face tension over how many programming languages they should support. But standardizing on just one is likely to be limiting — particularly when many enterprises favor giving dev teams a degree of autonomy. So if one is too few, how many is too many?
In this episode, our co-hosts Rebecca Parsons and Mike Mason are joined by Evan Bottcher, Technical Principal at ThoughtWorks Australia. Together they explore how enterprises can make practical decisions about language choices, so that their developers have the right tools for the right jobs. How can you put in place guard rails that ensure you’re able to maintain standards while giving developers enough autonomy?