On Wed, Nov 29, 2017 at 1:40 AM, Belinda Weaver <[email protected]> wrote: > Hi all > > Just saw this tweeted - https://sec.eff.org/articles/touching-devices > > Interesting piece on why taking over someone's device is a no-no.
Interesting--I've thought about this from time to time, but not usually too deeply. I think personally I'm usually pretty good on all these points. I can be patient in guiding students toward figuring things out on their own. The one area where there becomes a conflict is that (not too infrequent case) where we're about to start a workshop and it becomes more important for the student to have working software than to have gotten it working on their own (otherwise they'll be distracted during much of the lesson just trying to get their computer working, and (lacking the necessary skills to do so) end up giving up on their computer, and thus the rest of the workshop. I've seen this happen more than enough times and in those cases, with limited time, it's better if I can just get in there (with their permission of course, and as much explanation of what I'm doing as possible) and fix things. _______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/listinfo/discuss
