I usually take over someone's device when I don't know the answer to why something isn't working and need to poke around and run several diagnostic tests.
Trying to get them to run archaic commands that I'm not even sure will be part of the solution, or explaining what I'm checking for, seems like it would overload them at their current level and just leave them more confused. I general explain what it was once I know though. Thoughts? On Tue, Nov 28, 2017, 20:50 Paul Ivanov, <[email protected]> wrote: > ...and for those times where a discouraged learner wants to hand over > their keyboard to you - my go to phrase is "Go ahead, you drive" - > meaning I'll give directions, but not going to hold the steering > wheel. After all, it's their "vehicle". > > On 11/29/17, 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. > > > > regards > > Belinda > > > > Belinda Weaver > > Community Development Lead > > Software and Data Carpentry > > e: [email protected] | p: +61 408 841 882 | t: @cloudaus > > > > > -- > Paul Ivanov > http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 > _______________________________________________ > Discuss mailing list > [email protected] > http://lists.software-carpentry.org/listinfo/discuss
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/listinfo/discuss
