Today’s class discussion about affordances got me thinking about what it means to be a phile vs. a phobe … but I think the best way to think about that is in more of a dynamic way (like a continuum) rather than in oppositional terms. In terms of language teaching, I have experienced colleagues on many places along this continuum. 
When I was working as a faculty member at a community college in the ESL department, I was probably one of the more technophilish (technophilic?) team members. However, there were certainly some reticent individuals, and often it was difficult to feel like we were “making progress” unless they were on board.
Nevertheless, one of the benefits of having people with different perspectives is that it can expand the pool of ideas. One particular example that comes to mind is when we made a move in our department to use a cloud service for storage of program files (we were using a flash drive system that involved a cumbersome process of copying/distribution to many adjunct instructors). It was my idea that we could have a dedicated page on our LMS to house these files, but of course this was met with much opposition from some of the more technophobic faculty members. In particular, they were concerned that this would require a training session, which was time consuming. Their argument was that no one needed to be trained to use a flash drive, but that using an LMS would require some sort of workshop in which the adjunct instructors were trained in how to use the system to access the files they needed for teaching in our program. Which was TOTALLY true and something I had not even considered.
So, the benefit to having them voice this concern was that I devised a training session on accessing the course files via the LMS and used the full-time faculty as “guinea pigs” to pilot the program before extending it to use with all of the adjuncts. This helped me to work out the kinks and discover the “sticky spots” before the system went “live.”
If we had all been technophiles, this would’ve been much more difficult because we probably would’ve assumed that the system would be inherently better rather than brainstorming and troubleshooting the pitfalls. The lesson learned in all of this is related to affordance: We cannot effectively utilize technological systems (and access their affordances) without input from many different stakeholders with many different perspectives.