Thread by @securelyfitz

Hey Twitter: Reply to this tweet with things that you don't like about, and reasons you avoid technical training!

Why? I know there's people who avoid it for a number of reasons -
Worrying about holding the class back
Worrying about being asked questions on the spot
Worrying about their questions being criticized
Worrying about having to work with someone

I often get the impression that the people who might benefit most from training are ones who avoid it as well.

I've tried to mitigate these things, but I can only mitigate the issues I'm aware of. What else? What am I missing? What can I and other trainers do better?

Here are some things I try to do and recommend to other trainers. What should I add to the list?

(yes, eventually I'll compile & curate this, and post it long form)

Don't just ask the whole group if anyone has questions. Go and individually ask each person for questions too.

Even better, word it so 'no' isn't an answer. "What are you working on? What's giving you trouble?" gets better responses than "Do you have any questions?"

Pay attention to people who don't speak up. Some are more talkative than others, this breaks ice and helps discussion.

But - after a group discussion, follow up with anyone who was silent. They may have things to contribute but were overwhelmed by others more assertive.

I do have some labs I strongly encourage group work - but working together is optional, and I try to shuffle groups if it happens more than once.

Teamwork is important, but you're taking a class for technical content. Someone else's social issues shouldn't impede your learning.

Pay attention to interactions. I've had attendees spoil each others experience - with general negativity, &one case, constant criticism of a coworker.
'Separate' them by offering either of them an 'out' to work elsewhere or with someone else.
I've failed at this in the past. :(

Sometimes people misunderstand. Saying 'you're wrong' is direct but stifles conversation no matter how true.

"How did you come to that conclusion" deepens the conversation and lets you root cause the misunderstanding. "I think there's a better conclusion" helps too.

CTF isn't everything and isn't for everyone.

It works well for some, but many people don't learn that way. Unrushed focus time lets you fundamentally understand a whole problem instead of trivializing it by seeking out a single quick path through/around it.

Not everyone works at the same pace. If half the class is chatting, half the class thinks they're behind.

Have extra challenges for people who finish quickly. The last few steps of my labs start with "If time permits, repeat but..." or "If time permits, take a deeper look at..."

NEVER ask "Who isn't finished yet, can we move on?"

People who aren't finished and need the time are the last to speak up.

Try "We're going to work on this for X more minutes. Take a break if you need it, but let me know if you'd like me to come help you finish."

Don't trivialize feedback.

If someone takes the time to give feedback, take advantage of it and use it to improve things.

Sometimes, that means asking 'How do i revise my course description so someone like this won't take my class'

(P.S. If all the feedback is about the food, the room, or the color of the lights - that means your content is probably in good shape. Or that the food is really that bad)

ALWAYS ASK BEFORE TAKING PICTURES.
I often take pictures of people working in class - but hands and tools only and with permission.

Some conferences try to send photographers in to classrooms for photos. I ask them to leave on behalf of the attendees.

P.S. If you prefer, DM me or email me, and i'll try to aggregate the comments & reasons