I am looking at IRC use in comparison to Amish and Luddite relations to technology, but haven’t written up so much of it yet. However, there are some good academic articles on the topic too – for instance Lindsay Elms is looking at this from the Science and Technology Studies perspective:
Lindsay Ems; Amish Workarounds: Toward a Dynamic, Contextualized View of Technology Use
There are other articles in the bibliography here; http://amishamerica.com/technology/
If only, if only certain language ecosystems were similarly conservative!
I guess that’s looking at the wrong level. Just like society at large, there will always be a sizable group that always uses the newest an greatest.
Zooming in, though, I know quite a few people that seem to follow similar approaches. Being from the Ruby world, I know a lot of people that work incredibly effectively with stock Rails + a couple of very well chosen additions with good track record.
Their argument is similar: they only adopt only things where they are sure there is long-term maintenance. They prefer self-written extensions over external extensions (it gives them full control over their future). They are also fully understood within their company. But on the other hand, the same companies experiment with new tech very early on and then either adopt for a long time or don’t.
There’s an interesting effect there: they rarely speak at conferences or blog about that, because it does rarely introduce new things. It’s boring. Effective evaluation is nothing we speak about. Yet, I’m running under the assumption that companies effective at evaluating and learning the skills for what they need themselves are the ones we call “well-run” later. They aren’t fun day to day. They are incredibly fun to work with over the course of 3 years.
Sort of related with an example of an iPhone: http://patrickrhone.com/2016/09/09/an-amish-approach-to-technology/