>Enter Fred George (of Programmer Anarchy fame). Fred came on board as Chief Architect, and focused on supporting the organisational move from traditional enter

>Enter Fred George (of Programmer Anarchy fame). Fred came on board as Chief Architect, and focused on supporting the organisational move from traditional enterprise technology team to a nimbler, highly skilled organisation built around a strong culture of personal responsibility and trust. I think all the other details in this write-up are not as important as this. The specific tech choice isn't the driver, it is this cultural shift. This doesn't mean the tech choice doesn't matter though. In fact, I would argue that the most rapid way to build such a culture in your organization is to self-select for people who would do well in that environment. I hate painting people with too broad a brush, but my experience has been that choosing safe, established technologies as your stack will cause the sort of people who like safe, predictable work to show up for jobs. It can be hard (though certainly not impossible) to recruit the alpha geeks and the people with a more entrepreneurial perspective. There are plenty of super-talented people who have very pedestrian technologies as their preferred platforms. But if you're looking to mix things up quickly and go for a more nontraditional environment, the shortcut to getting that is to choose tech that is beloved by people who primarily want to work in a nontraditional manner. The sort of person who dabbles with go or node in their spare time does it not because they expect that it's going to be their meal ticket to a cushy job doing software development at a bank somewhere. They do it because they have got intrinsic motivation to learn new things and be on the cusp of the latest tech out of sheer enjoyment.